#27683: Change default transaction isolation level to READ COMMITTED on MySQL
-------------------------------------+-------------------------------------
Reporter: Shai Berger | Owner: Shai
Type: | Berger
Cleanup/optimization | Status: assigned
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
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 Shai Berger):
The system check was suggested by Adam in comment:1, and I thought the
analogy with strict-mode holds. I felt odd about there being both the
check and the deprecation warning (and commented about it in the original
PR) but yes, I felt that the fact they were both mostly silent (the check
is only vocal in `migrate` by default) sort-of justifies keeping both.
--
Ticket URL: <https://code.djangoproject.com/ticket/27683#comment:16>
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.a4e13d619943150473ebb4012354798d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
