#27762: Concurrency Safety Documentation
-------------------------------------+-------------------------------------
Reporter: Kevin Mahoney | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Documentation | Version: 1.10
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Someday/Maybe
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham):
* type: Uncategorized => Cleanup/optimization
* stage: Unreviewed => Someday/Maybe
Comment:
There is some discussion of isolation on the
[https://docs.djangoproject.com/en/dev/ref/databases/ databases reference
page]. I'm not sure how much more detail is needed. I think if you're at
the point of changing the isolation level, you probably know why you need
to change it and what the consequences are.
Django 1.11 added an easy option for changing the isolation level on
MySQL. Django 2.0 is likely to switch the default level to READ COMMITTED
(#27683).
By the way, you'll reach a wider audience if you write to the
DevelopersMailingList about your ideas for documentation enhancements.
--
Ticket URL: <https://code.djangoproject.com/ticket/27762#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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.88e0d3f7e4b960320e5f538314e189a1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
