Re: unable to see SQL even after DEBUG=True in settings

On Oct 16, 8:22 pm, Javier Guerra <jav...@guerrag.com> wrote:
> On Fri, Oct 16, 2009 at 1:55 AM, Jani Tiainen <rede...@gmail.com> wrote:
> >> I have run the app such that it has executed number of db queries and I
> >> know for sure there must be some sql.  But still I don't see any in
> >> connection.queries.  what am I doing wrong?
>
> > Are you sure that querysets are evaluated? Meaning that you actually
> > access them, just create querysets.
>
> also, from the transcript you send, it's not obvious if you actually
> run the app in the same python process or if it's running separately
> and you'd want to magically see the effect in an independent
> interpreter
>

Putting the code in the view showed the sql. You were right. The app
was running on a different process and my interpreter spawned a
different one! Thanks for pointing me in the right direction. silly
me!

thanks Javier, Jani

Indu
--~--~---------~--~----~------------~-------~--~----~
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+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---