#23820: Make it possible to override USE_TZ & TIME_ZONE on a per-database basis
-------------------------------------+-------------------------------------
Reporter: aaugustin | Owner: nobody
Type: New | Status: new
feature | Version: master
Component: Database | Keywords:
layer (models, ORM) | Has patch: 0
Severity: Normal | Needs tests: 0
Triage Stage: | Easy pickings: 0
Unreviewed |
Needs documentation: 0 |
Patch needs improvement: 0 |
UI/UX: 0 |
-------------------------------------+-------------------------------------
When integrating with a legacy database, datetimes are most often encoded
in local time. This doesn't work well with projects where `USE_TZ = True`.
The configuration for each database backend should accept a `TIME_ZONE`
option to enforce interpretation of datetimes stored in that database as
naive values in that time zone.
Setting this option when `USE_TZ = False` could either be an error or
perform a conversion to the global default `TIME_ZONE`. The latter may be
too complicated to be worth the effort.
--
Ticket URL: <https://code.djangoproject.com/ticket/23820>
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/052.aa6678739cd836ffb712a9eb13c66f3f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
