#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):
At a first approximation, I suspect it is better to be cautious about this
sort of change. However, this may be a good question to ask the community.
The deprecation period may be required because although the warnings and
settings are at the project level, there may be code changes required at
the app level, and it may be better to keep the new projects aware of the
issue while 3rd parties adapt.
--
Ticket URL: <https://code.djangoproject.com/ticket/27683#comment:12>
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.0073125fffc4cdb9271884d0d2f30da4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
