diff options
| author | Tim Graham <timograham@gmail.com> | 2018-05-17 10:16:32 -0400 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2018-05-17 11:00:10 -0400 |
| commit | 7543ab1f8dcb20dbbdf6a41eace95fc47c8dcaa3 (patch) | |
| tree | 98e0f0cbec43f45ea36c09cafb97385bca028a9f /docs/ref/databases.txt | |
| parent | 1cbd3d7874a4887fa2a6d7ef582defc388429b97 (diff) | |
Removed versionadded/changed annotations for 2.0.
Diffstat (limited to 'docs/ref/databases.txt')
| -rw-r--r-- | docs/ref/databases.txt | 6 |
1 files changed, 0 insertions, 6 deletions
diff --git a/docs/ref/databases.txt b/docs/ref/databases.txt index 42743f36cc..8620db3c27 100644 --- a/docs/ref/databases.txt +++ b/docs/ref/databases.txt @@ -490,12 +490,6 @@ or ``None`` to use the server's configured isolation level. However, Django 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 Creating your tables |