From a228545026e30d3223b3fbb13a262b5e005101ae Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Tue, 31 Dec 2013 13:02:01 -0500 Subject: [PATCH] [1.6.x] Fixed #21484 -- Documented that SQL logging does not include "framework level" queries. Backport of 4d8d76e7a8 from master --- docs/topics/logging.txt | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/docs/topics/logging.txt b/docs/topics/logging.txt index 1a0b625886..0c7f7b7974 100644 --- a/docs/topics/logging.txt +++ b/docs/topics/logging.txt @@ -450,9 +450,9 @@ Messages to this logger have the following extra context: ``django.db.backends`` ~~~~~~~~~~~~~~~~~~~~~~ -Messages relating to the interaction of code with the database. -For example, every SQL statement executed by a request is logged -at the ``DEBUG`` level to this logger. +Messages relating to the interaction of code with the database. For example, +every application-level SQL statement executed by a request is logged at the +``DEBUG`` level to this logger. Messages to this logger have the following extra context: @@ -464,6 +464,11 @@ For performance reasons, SQL logging is only enabled when ``settings.DEBUG`` is set to ``True``, regardless of the logging 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 the view all database queries. + ``django.security.*`` ~~~~~~~~~~~~~~~~~~~~~~