#15527: django.db logger only works when DEBUG=True ------------------------------------------+--------------------------- Reporter: boxm | Owner: nobody Status: new | Milestone: Component: Database layer (models, ORM) | Version: 1.3-beta Keywords: logging | Triage Stage: Unreviewed Has patch: 0 | ------------------------------------------+--------------------------- The default django.db logger only gets the SQL of queries written to it when DEBUG=True.
This limitation is not documented, leading users to expect their query logging to work. Either the behaviour should be changed to always log (which would be preferred), or the documentation updated to reflect the DEBUG=True limitation. Justification for always logging, even if DEBUG != True is that it is extremely useful to be able to turn on logging for DB queries on a production system without triggering all the other behaviours that DEBUG=True causes. With the current setup this is impossible. The developer already has control over suppressing the logging if it is unwanted, so nothing is lost by allowing query logging always. -- Ticket URL: <http://code.djangoproject.com/ticket/15527> Django <http://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because you are subscribed to the Google Groups "Django updates" group. To post to this group, send email to django-updates@googlegroups.com. To unsubscribe from this group, send email to django-updates+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-updates?hl=en.
