diff options
| author | Tim Graham <timograham@gmail.com> | 2012-12-18 07:04:17 -0500 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2012-12-18 08:10:12 -0500 |
| commit | 31f49f1396c4cc565017066e9f17c6b850a89687 (patch) | |
| tree | 1a766fdde59419c1db9a1ad04e5ce75baba956b8 /docs | |
| parent | 7df03268a467a9aec9c4c574c85317a738ca33ae (diff) | |
| download | django-31f49f1396c4cc565017066e9f17c6b850a89687.tar.gz | |
Fixed #19442 - Clarified that raw SQL must be committed.
Thanks startup.canada for the suggestion.
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/topics/db/transactions.txt | 3 |
1 files changed, 2 insertions, 1 deletions
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 +<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. |