#17213: Can't change TIME_ZONE after initial transaction in PostgreSQL
-------------------------------------+-------------------------------------
Reporter: calvinspealman | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: SVN
(models, ORM) | Resolution: wontfix
Severity: Normal | Triage Stage:
Keywords: | Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by aaugustin):
In fact, you're looking a larger problem than just time zone settings.
(Massive) multi-hosting isn't supported by Django at this time. While it
sort of works (some third party libraries exist to support this use case),
our current position is that changing settings at runtime may cause
undefined behavior.
--
Ticket URL: <https://code.djangoproject.com/ticket/17213#comment:4>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
