#24318: Can't configure Postgres isolation level if using recent psycopg2
-------------------------------------+-------------------------------------
Reporter: carljm | Owner: aaugustin
Type: Bug | Status: closed
Component: Database layer | Version: 1.7
(models, ORM) |
Severity: Release blocker | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Aymeric Augustin <aymeric.augustin@…>):
In [changeset:"9b7d512d5fb88844d920929b3cbb9d6c38b8b891"]:
{{{
#!CommitTicketReference repository=""
revision="9b7d512d5fb88844d920929b3cbb9d6c38b8b891"
[1.7.x] Fixed #24318 -- Set the transaction isolation level with psycopg
>= 2.4.2.
Backport of 76356d96 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/24318#comment:13>
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.af63c3b64199647b2b84ba7514a95ab0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
