From 924af638e4d4fb8eb46a19ac0cafcb2e83480cf3 Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Wed, 1 Feb 2017 15:34:17 -0500 Subject: Fixed #27683 -- Made MySQL default to the read committed isolation level. Thanks Shai Berger for test help and Adam Johnson for review. --- docs/ref/databases.txt | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) (limited to 'docs/ref') diff --git a/docs/ref/databases.txt b/docs/ref/databases.txt index 26351314de..af368c8dd5 100644 --- a/docs/ref/databases.txt +++ b/docs/ref/databases.txt @@ -449,8 +449,14 @@ this entry are the four standard isolation levels: * ``'serializable'`` or ``None`` to use the server's configured isolation level. However, Django -works best with read committed rather than MySQL's default, repeatable read. -Data loss is possible with repeatable read. +works best with and defaults to read committed rather than MySQL's default, +repeatable read. Data loss is possible with repeatable read. + +.. versionchanged:: 2.0 + + In older versions, the MySQL database backend defaults to using the + database's isolation level (which defaults to repeatable read) rather + than read committed. .. _transaction isolation level: https://dev.mysql.com/doc/refman/en/innodb-transaction-isolation-levels.html -- cgit v1.3