#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 calvinspealman):
While I'm very happy to see #2626 moving forward, I don't think it will be
helpful in the context I've seen #17213 needed, which are installations
running more sites than can realistically be served with at least one
process per site, and some sort of middleware is used before each request
to load per-site settings. I understand the dislike of changing settings,
and I agree with it. i only filed this ticket, because it seemed that
#3459 had broken a previous behavior and I could not determine if this was
intended or desirable. I'm not sure the best course of action for such
setups in the future, but will give it some thought.
--
Ticket URL: <https://code.djangoproject.com/ticket/17213#comment:3>
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 django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
