On 1/8/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
It is hell optimizing content when you don't know where some of the queries are executing from, and if I was missing information, it'd be much easier to see that, than it would be to see that I've got X query executing in X template.
The debug cursor will show you every query executed, so you can find out how many queries you're running. Though I'm curious as to what sorts of queries you're having issues with; from the template system, the only ways you can get SQL to execute are * Attribute access of a related object which hadn't previously been accessed (and select_related will work around that for you so you get all the queries up-front). * Method accesses which fetch data (these should be documented in your models). * Template tags which execute SQL (these should be documented in the template tags which are executing the SQL). As far as I know, there are no other ways to execute SQL from a template; everything else should be taking place in the view (even context processors, because they're applied up-front). Are you finding database accesses coming from somewhere else? -- "May the forces of evil become confused on the way to your house." -- George Carlin --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
