Skip to content
This repository


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse code

Fixed #19442 - Clarified that raw SQL must be committed.

Thanks startup.canada for the suggestion.
  • Loading branch information...
commit 31f49f1396c4cc565017066e9f17c6b850a89687 1 parent 7df0326
Tim Graham authored December 18, 2012

Showing 1 changed file with 2 additions and 1 deletion. Show diff stats Hide diff stats

  1. 3  docs/topics/db/transactions.txt
3  docs/topics/db/transactions.txt
@@ -199,7 +199,8 @@ Requirements for transaction handling
199 199
 Django requires that every transaction that is opened is closed before
200 200
 the completion of a request. If you are using :func:`autocommit` (the
201 201
 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
+<executing-custom-sql>`). However, if you are manually managing
203 204
 transactions (using the :func:`commit_manually` decorator), you must
204 205
 ensure that the transaction is either committed or rolled back before
205 206
 a request is completed.

0 notes on commit 31f49f1

Please sign in to comment.
Something went wrong with that request. Please try again.