On Nov 4, 3:44 pm, Knut Nesheim <knut.nesh...@mtab.se> 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
> > HIDE_DJANGO_SQL (set to True by default), which makes django' function
> > calls not to appear in query stacktraces. If you set it to "False",
> > you will be able to see the whole stacktraces. You can read up on the
> > rest of the options on the related package index page (at least,
> > that's where I've learned about them).
>
> Thank you for your help.
>
> If I set this to False, I see all sql queries executed, but what I
> want is to see the actual python code responsible for executing the
> query in the first place. I've read the documentation on the options
> and I cannot find such an option.
>
> Regards
> Knut
> --
> Knut Nesheim | MTAB Transport & Spedition AB
> Box 20164 | SE-161 02 Bromma | Visiting address: Ranhammarsvägen 26
> Phone: +46 8 54 600 153
> E-mail: knut.nesh...@mtab.se | Web:www.mtab.se
>
> Vi utför alla uppdrag på grundval av NSAB 2000.
> All transactions are carried out according to our standard conditions
> covered by NSAB2000
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.
--~--~---------~--~----~------------~-------~--~----~
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
django-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
