#27683: Change default transaction isolation level to READ COMMITTED on MySQL
-------------------------------------+-------------------------------------
Reporter: Shai Berger | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | 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 Shai Berger):
So, with respect to the option to use checks and deprecation warnings:
1) We can deprecate whatever we like whenever we like, the LTS limitation
is only about removing deprecation shims in the same major version (so,
shim introduced in 1.11 **can** be removed in 2.1).
2) Annoyance stands, so I think the correct path is at least to minimize
it by explicitly supporting isolation-level in `OPTIONS`. That's also the
easy route (both for users and implementation) to deprecation.
--
Ticket URL: <https://code.djangoproject.com/ticket/27683#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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/063.ec6e3c494369108764f3da59179d6c5d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
