From a44439e880b75b57c26d4a907b83a4433268e4b4 Mon Sep 17 00:00:00 2001 From: Gary Wilson Jr Date: Fri, 15 Aug 2008 13:44:43 +0000 Subject: [PATCH] Fixed #8137 -- Replaced an outdated link in the transactions docs. git-svn-id: http://code.djangoproject.com/svn/django/trunk@8377 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/transactions.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/transactions.txt b/docs/transactions.txt index 2b0755a257..da7039cbab 100644 --- a/docs/transactions.txt +++ b/docs/transactions.txt @@ -126,8 +126,8 @@ Manual transaction management looks like this:: .. admonition:: An important note to users of earlier Django releases: The database ``connection.commit()`` and ``connection.rollback()`` methods - (called ``db.commit()`` and ``db.rollback()`` in 0.91 and earlier) no longer - exist. They've been replaced by ``transaction.commit()`` and + (called ``db.commit()`` and ``db.rollback()`` in 0.91 and earlier) no + longer exist. They've been replaced by ``transaction.commit()`` and ``transaction.rollback()``. How to globally deactivate transaction management @@ -160,4 +160,4 @@ in auto-commit mode: Statements will be executed and committed as soon as they're called. If your MySQL setup *does* support transactions, Django will handle transactions as explained in this document. -.. _information on MySQL transactions: http://dev.mysql.com/books/mysqlpress/mysql-tutorial/ch10.html +.. _information on MySQL transactions: http://dev.mysql.com/doc/refman/5.0/en/sql-syntax-transactions.html