Re: Trace SQL back to python statement

2009-11-04 Thread Knut Nesheim
4 nov 2009 kl. 14.21 skrev Mark L.: > When you are in the SQL tab, to the left of the actual query, isn't > there a "Toggle Stacktrace" link? Clicking it reveals the stacktrace, > which has precisely the information you need. This is a bit embarassing.. I downloaded django-debug-toolbar from gi

Re: Trace SQL back to python statement

2009-11-04 Thread Mark L.
On Nov 4, 3:44 pm, Knut Nesheim wrote: > 4 nov 2009 kl. 13.34 skrev Mark L.: > > > I guess by "debug toolbar" you mean the django-debug-toolbar (http:// > > pypi.python.org/pypi/django-debug-toolbar/0.8.0). If that is the case, > > django-debug-toolbar has a number of options and among them > >

Re: Trace SQL back to python statement

2009-11-04 Thread Knut Nesheim
4 nov 2009 kl. 13.34 skrev Mark L.: > I guess by "debug toolbar" you mean the django-debug-toolbar (http:// > pypi.python.org/pypi/django-debug-toolbar/0.8.0). If that is the case, > django-debug-toolbar has a number of options and among them > HIDE_DJANGO_SQL (set to True by default), which makes

Re: Trace SQL back to python statement

2009-11-04 Thread Mark L.
On Nov 4, 2:02 pm, Knut Nesheim wrote: > Hello all, > > I'm trying to do some profiling on an application so I know where to   > optimize and how I can expect it to perform with large datasets. I use   > the debug toolbar to inspect sql queries. > >  From time to time certain pages will generat

Trace SQL back to python statement

2009-11-04 Thread Knut Nesheim
Hello all, I'm trying to do some profiling on an application so I know where to optimize and how I can expect it to perform with large datasets. I use the debug toolbar to inspect sql queries. From time to time certain pages will generate ~100 duplicated extra queries. These pages lists or