On Apr 29, 9:32 am, leopay <[EMAIL PROTECTED]> wrote:
> oh,I make a mistake the first query is
>
> Entry.objects.all()[0:1]
>
> but still have the problem
This is to do with lazy evaluation of querysets. I've posted an
explanation on django-users - please reply there if you have any more
question
oh,I make a mistake the first query is
Entry.objects.all()[0:1]
but still have the problem
On Tue, Apr 29, 2008 at 3:10 PM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> I use django.core.context_processors.debug to see the sql_queries in
> template.
> The raw sql of query
>
> Entry.objects.all
On Tue, Apr 29, 2008 at 3:10 PM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> I use django.core.context_processors.debug to see the sql_queries in
> template.
...
Please don't cross post messages between django-users and
django-developers. You won't increase the number of readers - you can
I use django.core.context_processors.debug to see the sql_queries in
template.
The raw sql of query
Entry.objects.all()[0,1]
does not in the sql_queries,but if I change the query like this
Entry.objects.all()[0]
and then the sql is in the sql_queries. why?
--~--~-~--~~~
