#3460: postgresql_psycopg2 backend uses wrong isolation level
-------------------------------------------------+--------------------------
Reporter: Jack Moffitt <[EMAIL PROTECTED]> | Owner: nobody
Status: reopened | Component:
Database wrapper
Version: SVN | Resolution:
Keywords: | Stage:
Design decision needed
Has_patch: 1 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 1
-------------------------------------------------+--------------------------
Changes (by Jack Moffitt <[EMAIL PROTECTED]>):
* status: closed => reopened
* resolution: duplicate =>
Comment:
I'm reopening because reading #6064 it is clear this is not a duplicate.
That functionality is about initial SQL, and this functionality can not be
changed by SQL alone. We are changing the Python wrapper's functionality
here, not the database's.
There is nothing changing on the postgresql side. The default python DB-
API functionality is fine for easy of use, but is not what you want in a
system like Django, as it is extremely wasteful of transactions in the
common case. Note that this is specified by the DB-API spec, and will
probably affect every database with transactions. Each wrapper is going
to have its own way to turn this off I imagine.
--
Ticket URL: <http://code.djangoproject.com/ticket/3460#comment:13>
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
-~----------~----~----~----~------~----~------~--~---
