#18130: postgres_psycopg2 adapter uses hard coded isolation levels
----------------------------------------------+----------------------
Reporter: limscoder | Owner: nobody
Type: New feature | Status: new
Component: Database layer (models, ORM) | Version: 1.4
Severity: Normal | Keywords: postgres
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------------------+----------------------
Django's postgres_psycopg2 adapter sets the connection's isolation level
to psycopg2.extensions.ISOLATION_LEVEL_READ_COMMITTED when autocommit ==
False.
My application requires a more strict isolation level, so I am forced to
create a new backend and override DatabaseWrapper._set_isolation_level to
make sure the connection has the correct isolation level set.
There should be a configuration option within the database config in
settings.py that allows users to set the appropriate isolation level if
the default level is not correct for their application. It would also be
nice if there was an option to not set the isolation level at all, and
instead rely on the default isolation level provided by the Postgres
server.
--
Ticket URL: <https://code.djangoproject.com/ticket/18130>
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 [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.
