#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 timgraham):
I guess [e0449316] preceded the rest of the transactions overhaul in 1.6.
I'd favor removing the "Isolation level" section from the docs rather than
saying "this only works with psycopg2 < 2.4.2" as that seems a bit odd to
explain. What do you think?
--
Ticket URL: <https://code.djangoproject.com/ticket/24318#comment:5>
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.b0e286c3ea17390c96626168b4aa816d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
