#37014: SQLite emulation of db_default involving Extract/Trunc might
unexpectedly
apply overridden timezone for inserted values
-------------------------------------+-------------------------------------
Reporter: Jacob Walls | Owner: (none)
Type: Bug | Status: new
Component: Database layer | Version: 6.0
(models, ORM) |
Severity: Normal | Resolution:
Keywords: tzinfo, TIME_ZONE, | Triage Stage: Accepted
Extract, Trunc |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Simon Charette):
* stage: Unreviewed => Accepted
Comment:
I also think the second solution is the preferable one as there are likely
other expressions out there that rely on global state expected to be
captured at field definition time and might suffer from the same problem.
It also more aligned with how we've been doing things historically when
running into these kind of problems.
--
Ticket URL: <https://code.djangoproject.com/ticket/37014#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 view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019d420ba57d-5cdb3854-ff42-4108-bf31-043ec3f74077-000000%40eu-central-1.amazonses.com.
