#23820: Make it possible to override USE_TZ & TIME_ZONE on a per-database basis
-------------------------------------+-------------------------------------
Reporter: aaugustin | Owner: aaugustin
Type: New feature | Status: closed
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Aymeric Augustin <aymeric.augustin@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"ed83881e648771d22658f21b939f66e75c499864" ed83881]:
{{{
#!CommitTicketReference repository=""
revision="ed83881e648771d22658f21b939f66e75c499864"
Fixed #23820 -- Supported per-database time zone.
The primary use case is to interact with a third-party database (not
primarily managed by Django) that doesn't support time zones and where
datetimes are stored in local time when USE_TZ is True.
Configuring a PostgreSQL database with the TIME_ZONE option while USE_TZ
is False used to result in silent data corruption. Now this is an error.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/23820#comment:10>
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/067.f07d6da6af6c024b11aa097dad845d60%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
