#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
-------------------------------------+-------------------------------------
Comment (by Jure Erznožnik):
Removing auto_now=True solved the problem.
I still don't see how that IS the solution: I WAS using now() for date in
searc / create. auto_now should make o difference.
Thanks for the suggestion.
--
Ticket URL: <https://code.djangoproject.com/ticket/28445#comment:2>
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.18f1495153c60005ebb8437cd76b272e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
