innov
/
django1
1
0
Fork 0
Code Issues Pull Requests 1 Projects Releases Wiki Activity

Edited db/transactions.txt changes from [17341] 

git-svn-id: http://code.djangoproject.com/svn/django/trunk@17423 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Adrian Holovaty 2012-02-03 17:54:08 +00:00
parent f950a99acb
commit 6bbc85cd6a
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/topics/db/transactions.txt
View File

@ -226,13 +226,13 @@ Savepoints
========== ==========
A savepoint is a marker within a transaction that enables you to roll back part 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 of a transaction, rather than the full transaction. Savepoints are available
the PostgreSQL 8, Oracle and MySQL (version 5.0.3 and newer, when using the with the PostgreSQL 8, Oracle and MySQL (version 5.0.3 and newer, when using
InnoDB storage engine) backends. Other backends will provide the savepoint the InnoDB storage engine) backends. Other backends provide the savepoint
functions, but they are empty operations - they won't actually do anything. functions, but they're empty operations -- they don't actually do anything.
.. versionchanged:: 1.4 .. 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 Savepoints aren't especially useful if you are using the default
``autocommit`` behavior of Django. However, if you are using ``autocommit`` behavior of Django. However, if you are using