#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):
Historically support for isolation levels in the psycopg2 backend only
existed for people who wanted to switch to autocommit. This is now the
default.
That said, I'm not sure that any isolation level other than the default
actually works well with Django, and I don't remember if the docs reflect
that.
--
Ticket URL: <https://code.djangoproject.com/ticket/24318#comment:2>
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.eadeb7bc777b356e9dbfa3a5250eb7ff%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
