#27683: Change default transaction isolation level to READ COMMITTED on MySQL
-------------------------------------+-------------------------------------
Reporter: Shai Berger | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: master
(models, ORM) |
Severity: Release blocker | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 1
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Shai Berger):
Replying to [comment:1 Adam Chainz]:
> An alternative to changing the default would be to have a system check
highly recommending READ-COMMITTED [...] "Warning: In Django 2.1 the
default tx_isolation will change..."
That may indeed be the way to go. Two issues arise:
1) We need to make sure which deprecations can happen when (WRT our
deprecation policies around LTSs)
2) It may be seen as annoying: "if you know that it's correct to use that
other level, why don't you just go and do it? why bug me?"
The big advantage is that it completely solves my 2nd backward-
compatibility issue.
--
Ticket URL: <https://code.djangoproject.com/ticket/27683#comment:2>
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.3fcdd006fd9645fbd04090c776fe2c87%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
