#18130: postgres_psycopg2 adapter should not use hard coded isolation levels
-------------------------------------+-------------------------------------
Reporter: limscoder | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: 1.4
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: postgres | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by aaugustin):
* stage: Unreviewed => Accepted
Comment:
Yes, we could provide a way to switch to "serializable" for people with
high concurrency and integrity requirements.
IIRC, under the "serializable" isolation level, the application should be
prepared to handle transaction failures (and possibly retry) on every
database query. I'm not sure we can handle this automatically in Django
without introducing magic. It deserves a fat warning in the documentation.
This isolation level is for people who know what they're doing :)
NB: there is some material on this topic in #3460.
--
Ticket URL: <https://code.djangoproject.com/ticket/18130#comment:3>
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 django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
