On Wed, 2008-09-24 at 20:45 -0700, Chris wrote: > I'm trying to debug a usage of callproc, which doesn't return any rows > when used inside Django. Is there anyway to view the SQL and escaped > values sent from db cursor?
There is no public API in the Python database wrappers to determine how the values are escaped, so the second part of that question is "no". > I found > http://docs.djangoproject.com/en/dev/faq/models/#how-can-i-see-the-raw-sql-queries-django-is-running > by this doesn't show anything. When they say "just do this", are they > implying we should run that from a manage.py shell? Yes. It only works when DEBUG=True, since connection.queries saves a record of every query run in each request, which can sometimes consume a lot of memory. Alternatively, if you have a queryset, you can see the SQL it is about to run (before it is executed) by looking at the output of my_queryset.query.as_sql() That will work always, since it is exactly how Django generates the SQL that it sends to the database (it returns a string and the list of parameters that are substituted into the query). Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
