From e11bd5c5ac0c7d85723451f8da7b6ad30fefc680 Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Tue, 18 Dec 2012 07:04:17 -0500 Subject: [PATCH] [1.5.X] Fixed #19442 - Clarified that raw SQL must be committed. Thanks startup.canada for the suggestion. Backport of 31f49f1396 from master --- docs/topics/db/transactions.txt | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/topics/db/transactions.txt b/docs/topics/db/transactions.txt index 65944abb8b..e3c2cadf6d 100644 --- a/docs/topics/db/transactions.txt +++ b/docs/topics/db/transactions.txt @@ -199,7 +199,8 @@ Requirements for transaction handling Django requires that every transaction that is opened is closed before the completion of a request. If you are using :func:`autocommit` (the default commit mode) or :func:`commit_on_success`, this will be done -for you automatically. However, if you are manually managing +for you automatically (with the exception of :ref:`executing custom SQL +`). However, if you are manually managing transactions (using the :func:`commit_manually` decorator), you must ensure that the transaction is either committed or rolled back before a request is completed.