test0908
/
django
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

[1.5.X] Fixed #19442 - Clarified that raw SQL must be committed. 

Thanks startup.canada for the suggestion.

Backport of 31f49f1396 from master
This commit is contained in:
Tim Graham 2012-12-18 07:04:17 -05:00
parent 2545dc59bf
commit e11bd5c5ac
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
docs/topics/db/transactions.txt
View File

@ -199,7 +199,8 @@ Requirements for transaction handling
Django requires that every transaction that is opened is closed before Django requires that every transaction that is opened is closed before
the completion of a request. If you are using :func:`autocommit` (the the completion of a request. If you are using :func:`autocommit` (the
default commit mode) or :func:`commit_on_success`, this will be done 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
transactions (using the :func:`commit_manually` decorator), you must transactions (using the :func:`commit_manually` decorator), you must
ensure that the transaction is either committed or rolled back before ensure that the transaction is either committed or rolled back before
a request is completed. a request is completed.