http://code.djangoproject.com/ticket/7121 :-)
--~--~-~--~~~---~--~~
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,
I was having a look at the code in order to find out what is going on.
First thing I noticed is the set_limit method of sql/query.py. The
high_mark is computed as follows:
self.high_mark = min(self.high_mark, self.low_mark + high)
Shouldn't it be max instead of min? Just wondering.
After I
HAI
On 4/29/08, lars <[EMAIL PROTECTED]> wrote:
>
>
> Hi all,
>
> I was playing around with object.filter when I noticed something funny
> in my postgresql.log.
> This is my query in the view:
>
>prev_and_current =
> Article.objects.filter(id__lte=article_id).order_by('-id')[0:2]
>
Hi all,
I was playing around with object.filter when I noticed something funny
in my postgresql.log.
This is my query in the view:
prev_and_current =
Article.objects.filter(id__lte=article_id).order_by('-id')[0:2]
article = prev_and_current[0]
prev_article =
4 matches
Mail list logo