diff options
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/releases/1.4.txt | 3 | ||||
| -rw-r--r-- | docs/topics/db/transactions.txt | 13 |
2 files changed, 11 insertions, 5 deletions
diff --git a/docs/releases/1.4.txt b/docs/releases/1.4.txt index 0cb30d633a..de7afc83c3 100644 --- a/docs/releases/1.4.txt +++ b/docs/releases/1.4.txt @@ -553,6 +553,9 @@ Django 1.4 also includes several smaller improvements worth noting: password reset mechanism and making it available is now much easier. For details, see :ref:`auth_password_reset`. +* The MySQL database backend can now make use of the savepoint feature + implemented by MySQL version 5.0.3 or newer with the InnoDB storage engine. + Backwards incompatible changes in 1.4 ===================================== diff --git a/docs/topics/db/transactions.txt b/docs/topics/db/transactions.txt index b2ee26d6b0..6e6754a9d8 100644 --- a/docs/topics/db/transactions.txt +++ b/docs/topics/db/transactions.txt @@ -225,11 +225,14 @@ transaction middleware, and only modify selected functions as needed. Savepoints ========== -A savepoint is a marker within a transaction that enables you to roll back -part of a transaction, rather than the full transaction. Savepoints are -available to the PostgreSQL 8 and Oracle backends. Other backends will -provide the savepoint functions, but they are empty operations - they won't -actually do anything. +A savepoint is a marker within a transaction that enables you to roll back part +of a transaction, rather than the full transaction. Savepoints are available to +the PostgreSQL 8, Oracle and MySQL (version 5.0.3 and newer, when using the +InnoDB storage engine) backends. Other backends will provide the savepoint +functions, but they are empty operations - they won't actually do anything. + +.. versionchanged:: 1.4 + Savepoint support when using the MySQL backend was added in Django 1.4 Savepoints aren't especially useful if you are using the default ``autocommit`` behavior of Django. However, if you are using |