#3459: SET TIME ZONE called too often for postgresql_psycopg2 backend
-------------------------------------------------+--------------------------
Reporter: Jack Moffitt <[EMAIL PROTECTED]> | Owner: adrian
Status: new | Component:
Database wrapper
Version: SVN | Resolution:
Keywords: | Stage:
Unreviewed
Has_patch: 1 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
-------------------------------------------------+--------------------------
Changes (by Jack Moffitt <[EMAIL PROTECTED]>):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
Note: According to postgresql 8.1 docs, this is correct:
http://www.postgresql.org/docs/8.1/interactive/sql-set.html
The SET will take effect for the entire session unless something else
calls set. This is regardless of whether it is inside a transaction or
not. However, the patch needs to be changed to do a COMMIT otherwise the
change will not take effect if this cursor's first transaction ends in a
rollback. I've attached a modified patch which also combines the fix for
#3460, which needs a similar setup.
I've also attached a test script to show that this works regardless of the
isolation level used.
--
Ticket URL: <http://code.djangoproject.com/ticket/3459#comment:1>
Django Code <http://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
-~----------~----~----~----~------~----~------~--~---
