#24318: Can't configure Postgres isolation level if using recent psycopg2
-------------------------------------+-------------------------------------
Reporter: carljm | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.7
(models, ORM) |
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by aaugustin):
psycopg2 2.4.2+ correctly separates the notions of autocommit and
isolation levels. I don't want to mix them again in Django
We can fix this bug by setting the isolation level with
[http://initd.org/psycopg/docs/connection.html#connection.set_session
set_session] in init_connection_state.
We could also tell people to configure the default isolation level in
their database server's configuration, but since it's easy to fix the
regression, I don't like this solution.
--
Ticket URL: <https://code.djangoproject.com/ticket/24318#comment:6>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.ad800e4dafe810d4dc55e3893e482f8f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
