#3460: postgresql_psycopg2 backend uses wrong isolation level
--------------------------------------------------------+-------------------
Reporter: Jack Moffitt <[EMAIL PROTECTED]> | Owner: cgrady
Status: new | Milestone:
Component: Database layer (models, ORM) | Version: SVN
Resolution: | Keywords:
Stage: Design decision needed | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 1 |
--------------------------------------------------------+-------------------
Comment (by Richard Davies <[EMAIL PROTECTED]>):
I've just updated Collin Grady's patch to apply against Django 1.0 (r8961)
and also current trunk.
Mostly minor reformatting work, but one significant change - [8314]
introduced savepoint support for Postgresql, which we need to turn off
when we are outside a transaction.
Issues: Although the patch applies again, it leaves a Django which does
not support any transaction behavior other than autocommit (leading to
various test suite failures). The problem is that django/db/transaction.py
also needs to be rewritten to actually create transactions (i.e. issue SQL
BEGIN/COMMIT or BEGIN/ROLLBACK) on top of the connection when the user
explicitly requests them. My proposed solution is for discussion at
http://groups.google.com/group/django-developers/msg/4e5171056b3f6558
--
Ticket URL: <http://code.djangoproject.com/ticket/3460#comment:20>
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 [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
-~----------~----~----~----~------~----~------~--~---
