On Thu, Feb 17, 2011 at 5:01 AM, Amar <amarsahino...@gmail.com> wrote:
> OK, I've created a barebone app which shows this problem, so if anyone > can try this and duplicate, I'll report this as a bug (unless there is > a problem wih my code) > You can get it here http://rapidshare.com/files/448393624/problem.zip > > I'm using PostgreSQL database, so change accordingly (unless it only > occurs when using PostgreSQL, which I doubt). > In fact I suspect the behavior is likely observed only on PostgreSQL, due to your queryset having no ordering defined. In that case PostgreSQL often will return the same element for different OFFSET values (any DB could do this, but PostgreSQL is the only one where I've seen it happening regularly). This ticket describes the problem: http://code.djangoproject.com/ticket/9006 Fix is to force force an ordering on the queryset or turn it into a list before indexing into it. Karen -- http://tracey.org/kmt/ -- 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.
