#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:
| Someday/Maybe
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Nir Izraeli):
Hi, I encountered a related issue and opened (and later answered) a
stackoverflow question I think may be useful for others stumbling upon
this ticket, so I'm linking it here:
https://stackoverflow.com/a/51399292/1146713
The gist of it is I was using an old MariaDB version (10.0) which
defaulted to {{{BINLOG_FORMAT = STATEMENT}}} instead of the more flexible
{{{BINLOG_FORMAT = MIXED}}} that is the default since version 10.2.4.
Django may want to add that as part of the default-override, to avoid this
problem when working with older versions of MariaDB, or include as part of
the documentation section about changing the default transaction isolation
level. I have no opinion on the matter but I'm up to contribute a change
once it's decided.
--
Ticket URL: <https://code.djangoproject.com/ticket/28901#comment:4>
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.fd48323c912a1c96ff32b84f4f2fb65f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
