Comments on: Django trap with LIMIT queries

By: Rich jones

Rich jones — Wed, 15 Feb 2012 20:41:41 +0000

Handy little post!

By: Eric

Eric — Wed, 19 Jan 2011 14:57:16 +0000

Great tip! It sounds like you’ve been using python for a while. I’ll have to give this idea a try!

By: Nicky Swift

Nicky Swift — Wed, 24 Nov 2010 23:09:13 +0000

Damn, certainly nice info. Where can I find that subscription?

Nicky Swift
bug detection device

By: Cal Leeming (sleepycal)

Cal Leeming (sleepycal) — Fri, 11 Dec 2009 00:50:30 +0000

Hey dude,

Thank you ever so much for giving these examples, it has really speeded up my query sets! I don’t know why they don’t list these sorts of things on the django documentation.. Ah well, good work dude!

Cal

By: Bertrand Mathieu

Bertrand Mathieu — Tue, 24 Mar 2009 09:29:28 +0000

I got this kind of problem with django 1.0 in admin site: when filling forms in formsets objects the code uses slices. Then the query with “LIMIT” return the same object at index 0 and 1! :-/
The “all()” does not uses LIMIT. My DB is postgres, maybe it is specific.

My workaround was to specify explicitely “ordering” on primary key (”id”) in the model definition.

By: Unode

Unode — Wed, 05 Nov 2008 20:17:35 +0000

The current version of django no longer has this trap. Using slices with or without the explicit list call will always give the same result.

Cheers

By: Dog training

Dog training — Thu, 22 Nov 2007 19:02:59 +0000

Very interesting… as always! Cheers from Switzerland.

By: Martina

Martina — Tue, 27 Feb 2007 22:23:29 +0000

instead of:
Item.objects.all()[2:4:1]
I prefer to write:
items = list(Item.objects.all()[2:4])
this states the intent much more explicit IMO.