From a001f3c31e751e6ab1622ae7f65f7f8aeca2ef9a Mon Sep 17 00:00:00 2001 From: Aymeric Augustin Date: Fri, 14 Dec 2012 21:15:48 +0100 Subject: Fixed #2304 -- Documented TRANSACTIONS_MANAGED. --- docs/topics/db/transactions.txt | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) (limited to 'docs/topics') diff --git a/docs/topics/db/transactions.txt b/docs/topics/db/transactions.txt index 3c0ec4f187..65944abb8b 100644 --- a/docs/topics/db/transactions.txt +++ b/docs/topics/db/transactions.txt @@ -208,11 +208,13 @@ This applies to all database operations, not just write operations. Even if your transaction only reads from the database, the transaction must be committed or rolled back before you complete a request. +.. _deactivate-transaction-management: + How to globally deactivate transaction management ================================================= Control freaks can totally disable all transaction management by setting -``DISABLE_TRANSACTION_MANAGEMENT`` to ``True`` in the Django settings file. +:setting:`TRANSACTIONS_MANAGED` to ``True`` in the Django settings file. If you do this, Django won't provide any automatic transaction management whatsoever. Middleware will no longer implicitly commit transactions, and -- cgit v1.3