#28901: Document considerations with read committed isolation level and InnoDB
-------------------------------------+-------------------------------------
Reporter: Dirkjan Ochtman | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Documentation | Version: 2.0
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Dirkjan Ochtman):
I wouldn't mind typing up the above in a way that is feasible for the
documentation -- however, it would sure be nice if someone with deeper
knowledge of Django and MySQL reviews that what I'm saying is correct and
makes sense, and simply reverting the isolation level is the best solution
here. It sure doesn't feel like the right solution -- but I couldn't
figure out so far what the best alternative is.
--
Ticket URL: <https://code.djangoproject.com/ticket/28901#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 [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/061.74de2a71be9c6986edf450b9adfdebb2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
