summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTim Graham <timograham@gmail.com>2013-12-31 13:02:01 -0500
committerTim Graham <timograham@gmail.com>2013-12-31 13:02:01 -0500
commit4d8d76e7a89858932b6f4f280a0ebf4cf94ab4b7 (patch)
treec702c15a6b684834239865228ba8891cb4d84d36
parentb8e3373f458aa363d59c61b58be390a5a1156467 (diff)
Fixed #21484 -- Documented that SQL logging does not include "framework level" queries.
-rw-r--r--docs/topics/logging.txt11
1 files changed, 8 insertions, 3 deletions
diff --git a/docs/topics/logging.txt b/docs/topics/logging.txt
index 03145fc41d..751563e4b9 100644
--- a/docs/topics/logging.txt
+++ b/docs/topics/logging.txt
@@ -441,9 +441,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:
@@ -455,6 +455,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.*``
~~~~~~~~~~~~~~~~~~~~~~