|
@@ -226,13 +226,13 @@ 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, 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.
|
|
|
+of a transaction, rather than the full transaction. Savepoints are available
|
|
|
+with the PostgreSQL 8, Oracle and MySQL (version 5.0.3 and newer, when using
|
|
|
+the InnoDB storage engine) backends. Other backends provide the savepoint
|
|
|
+functions, but they're empty operations -- they don't actually do anything.
|
|
|
|
|
|
.. versionchanged:: 1.4
|
|
|
- Savepoint support when using the MySQL backend was added in Django 1.4
|
|
|
+ Savepoint support for 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
|