Whether or not actions must me performed on `TIME_ZONE` and `USE_TZ`
change should be delegated to the backend specific connection and signal
receivers should only have to clear possibly stale cached values.
--
Ticket URL: <https://code.djangoproject.com/ticket/26712>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* needs_tests: 0 => 1
Comment:
[https://github.com/django/django/pull/6731 PR]
--
Ticket URL: <https://code.djangoproject.com/ticket/26712#comment:1>
* needs_docs: 0 => 1
* has_patch: 0 => 1
* stage: Unreviewed => Accepted
--
Ticket URL: <https://code.djangoproject.com/ticket/26712#comment:2>
* needs_docs: 1 => 0
* needs_tests: 1 => 0
Comment:
(I had accidently checked ''needs tests'' instead of ''has patch'' when I
linked to the PR)
--
Ticket URL: <https://code.djangoproject.com/ticket/26712#comment:3>
* stage: Accepted => Ready for checkin
--
Ticket URL: <https://code.djangoproject.com/ticket/26712#comment:4>
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"b484f167bed61f4cff215208eddf98a0655239d4" b484f167]:
{{{
#!CommitTicketReference repository=""
revision="b484f167bed61f4cff215208eddf98a0655239d4"
Fixed #26712 -- Avoided unnecessary SET TIMEZONE queries on PostgreSQL.
A change of the USE_TZ or TIME_ZONE settings doesn't necessarily require a
change to the active connections' timezones.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/26712#comment:5>
Comment (by Simon Charette <charette.s@…>):
In [changeset:"271581df606b307d89c141e8b1a50ace763bea81" 271581df]:
{{{
#!CommitTicketReference repository=""
revision="271581df606b307d89c141e8b1a50ace763bea81"
Refs #26712 -- Removed workarounds for PostgreSQL queries on TIME_ZONE
changes.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/26712#comment:6>