#28445: DateField timezone issue with get_or_create (duplicate key value
violates
unique constraint)
-------------------------------------+-------------------------------------
Reporter: Jure Erznožnik | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 1.10
(models, ORM) |
Severity: Normal | Resolution: needsinfo
Keywords: orm timezone | Triage Stage:
get_or_create | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham):
* status: new => closed
* resolution: => needsinfo
Comment:
The `date=timezone.now().date()` code looks suspicious. Since the field
has `auto_now=True`, it uses
[https://github.com/django/django/blob/99e7bba443e3ff1a115d930dbb6dfcf9bccb027c/django/db/models/fields/__init__.py#L1249
datetime.date.today()] as the creation value, regardless of you provide.
I'd suggest replacing `date=timezone.now().date()` with
`date=datetime.date.today()` and checking if the issue still happens.
Please reopen the ticket if you identify that Django is really at fault.
--
Ticket URL: <https://code.djangoproject.com/ticket/28445#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.bb54ab7abf159d755c3e2d498a1b004e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
