#28901: Read committed isolation level does not work with InnoDB
-----------------------------------------+------------------------
Reporter: djc | Owner: nobody
Type: Uncategorized | Status: new
Component: Documentation | Version: 2.0
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-----------------------------------------+------------------------
After upgrading my application to Django 2.0, I have been seeing errors:
"Cannot execute statement: impossible to write to binary log since
BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine
limited to row-based logging. InnoDB is limited to row-logging when
transaction isolation level is READ COMMITTED or READ UNCOMMITTED."
The 2.0 release notes at
https://docs.djangoproject.com/en/2.0/releases/2.0/#default-mysql-
isolation-level-is-read-committed don't mention anything about this
particular problem. Since, as far as I can tell, InnoDB and BINLOG_FORMAT
= STATEMENT are the default values, it would be useful if the
documentation could warn about this problem.
--
Ticket URL: <https://code.djangoproject.com/ticket/28901>
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/046.c2a939f3aeb45b687bd181f5a97ae594%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
