From 6bbc85cd6a32a0208586b291b82b08b1b9f0399f Mon Sep 17 00:00:00 2001 From: Adrian Holovaty Date: Fri, 3 Feb 2012 17:54:08 +0000 Subject: [PATCH] Edited db/transactions.txt changes from [17341] git-svn-id: http://code.djangoproject.com/svn/django/trunk@17423 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/topics/db/transactions.txt | 10 +++++----- 1 file 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