On 3/11/07, Laurie <[EMAIL PROTECTED]> wrote: > Ah, that might help if I can figure out where to call it from... Is > the list preserved across requests? Could I implement a view that I > could hit whenever I need to check 'what just happened to the > database'?
The query list only lives as long as the database connection, and Django doesn't persist connections. If you just want to see what's happening on the current request, the 'debug' context processor[1] will make the information available to templates as a 'sql_queries' variable, so you could drop something into the admin change list template which, say, prints out 'sql_queries' inside an HTML comment. Another option, if you want to log them over time, would be to create a middleware class with a 'process_response' method -- it will be called after each view has returned a response, and you could import the DB connection there and write out the queries to a file. [1] http://www.djangoproject.com/documentation/templates_python/#django-core-context-processors-debug -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
