That's fine, and useful indeed, but I need a bit more detail: I'm hunting for duplicate queries. Is there a possibility to tell where django fires those queries?
thanks On Aug 29, 6:38 pm, Tim Chase <[EMAIL PROTECTED]> wrote: > > How to view thesqlquerystatement involved in a django web page for > > optimization? thx > > http://www.djangoproject.com/documentation/faq/#how-can-i-see-the-raw... > > Just make sure DEBUG is False in a production environment, or > this is one of the first things that will kill your server > performance. > > -tim --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
