#3460: Allow configuration of postgresql_psycopg2 isolation level
--------------------------------------------------------+-------------------
Reporter: Jack Moffitt <metaj...@gmail.com> | Owner:
Richard Davies <richard.dav...@elastichosts.com>
Status: new | Milestone:
Component: Database layer (models, ORM) | Version: SVN
Resolution: | Keywords:
Stage: Accepted | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
--------------------------------------------------------+-------------------
Comment (by iamseb):
I've added an updated patch that implements a safe version of the
transaction isolation patch for database connections that implement
transaction pooling, whilst sticking with the implementation approach in
Richard's combined patch. Transaction isolation can return incorrect data
when retrieving PKs after insert operations without this addition.
--
Ticket URL: <http://code.djangoproject.com/ticket/3460#comment:32>
Django <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 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
-~----------~----~----~----~------~----~------~--~---
