diff options
| author | Adrian Holovaty <adrian@holovaty.com> | 2012-02-03 17:54:08 +0000 |
|---|---|---|
| committer | Adrian Holovaty <adrian@holovaty.com> | 2012-02-03 17:54:08 +0000 |
| commit | 6bbc85cd6a32a0208586b291b82b08b1b9f0399f (patch) | |
| tree | bb958adf56f062ba21bc508e234df9da61db122a | |
| parent | f950a99acbc2e881389cfb64c6bc5a021d467d7f (diff) | |
Edited db/transactions.txt changes from [17341]
git-svn-id: http://code.djangoproject.com/svn/django/trunk@17423 bcc190cf-cafb-0310-a4f2-bffc1f526a37
| -rw-r--r-- | docs/topics/db/transactions.txt | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/docs/topics/db/transactions.txt b/docs/topics/db/transactions.txt index 6e6754a9d8..0f0b52aa1e 100644 --- a/docs/topics/db/transactions.txt +++ b/docs/topics/db/transactions.txt @@ -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 |