#17062: Using postgres, if you rollback the first transaction on a connection,
the
effect of settings.TIME_ZONE is lost
-------------------------------------+-------------------------------------
Reporter: mwhudson | Owner: aaugustin
Type: Bug | Status: new
Component: Database layer | Version: 1.3
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by aaugustin):
akaariai, is there a reason why your patch changes the isolation level
rather than just calling `transaction.commit()` after the `SET TIME ZONE`
query?
FYI, I just committed a patch to use the constants for isolation levels
(r17112).
Optimizing the case when `settings.TIME_ZONE` is PostgreSQL's default time
zone could save 1 query per request (if I understand correctly). I suppose
we'd check the server timezone with
[http://initd.org/psycopg/docs/connection.html?highlight=timezone#connection.get_parameter_status
get_parameter_status]. Would you mind opening a separate ticket for this?
--
Ticket URL: <https://code.djangoproject.com/ticket/17062#comment:8>
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.
