From 798e38c2b9c46ab72e2ee8c33dc822f01b194b1e Mon Sep 17 00:00:00 2001 From: Ilya Bass Date: Thu, 20 Oct 2022 15:14:35 -0700 Subject: Fixed #31090 -- Logged transaction management queries. Thanks to Petter Strandmark for the original idea and Mariusz Felisiak for advice during the DjangoConUS 2022 Sprint! --- docs/ref/logging.txt | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) (limited to 'docs/ref') diff --git a/docs/ref/logging.txt b/docs/ref/logging.txt index ba443a0a36..edd9f21ecb 100644 --- a/docs/ref/logging.txt +++ b/docs/ref/logging.txt @@ -196,9 +196,13 @@ For performance reasons, SQL logging is only enabled when level or handlers that are installed. This logging does not include framework-level initialization (e.g. -``SET TIMEZONE``) or transaction management queries (e.g. ``BEGIN``, -``COMMIT``, and ``ROLLBACK``). Turn on query logging in your database if you -wish to view all database queries. +``SET TIMEZONE``). Turn on query logging in your database if you wish to view +all database queries. + +.. versionchanged:: 4.2 + + Support for logging transaction management queries (``BEGIN``, ``COMMIT``, + and ``ROLLBACK``) was added. .. _django-security-logger: -- cgit v1.3