Ticket #16492: 16492.diff
File 16492.diff, 1.6 KB (added by , 13 years ago) |
---|
-
docs/topics/db/transactions.txt
204 204 if your transaction only reads from the database, the transaction must 205 205 be committed or rolled back before you complete a request. 206 206 207 .. _topics-db-transactions-deactivate-management: 208 207 209 How to globally deactivate transaction management 208 210 ================================================= 209 211 210 212 Control freaks can totally disable all transaction management by setting 211 ``DISABLE_TRANSACTION_MANAGEMENT`` to ``True`` in the Django settings file.213 :setting:`TRANSACTIONS_MANAGED` to ``False`` in the Django settings file. 212 214 213 215 If you do this, Django won't provide any automatic transaction management 214 216 whatsoever. Middleware will no longer implicitly commit transactions, and -
docs/ref/settings.txt
1932 1932 1933 1933 .. _See available choices: http://www.postgresql.org/docs/8.1/static/datetime-keywords.html#DATETIME-TIMEZONE-SET-TABLE 1934 1934 1935 .. setting:: TRANSACTIONS_MANAGED 1936 1937 TRANSACTIONS_MANAGED 1938 -------------------- 1939 1940 Default: ``True`` 1941 1942 Set this to ``False`` if you want to disable all transaction management. This 1943 setting is only useful if you do exotic things with your database. See 1944 :ref:`topics-db-transactions-deactivate-management`. 1945 1935 1946 .. setting:: URL_VALIDATOR_USER_AGENT 1936 1947 1937 1948 URL_VALIDATOR_USER_AGENT