On Tuesday, March 26, 2013 10:47:34 PM UTC+1, Petite Abeille wrote: > > > On Mar 26, 2013, at 10:03 PM, Alex Gaynor <[email protected]<javascript:>> > wrote: > > > For what it's worth, SQL2011 does define OFFSET, finally. > > Perhaps worthwhile mentioning as well : > > "Do not try to implement a scrolling window using LIMIT and OFFSET. Doing > so will become sluggish as the user scrolls down toward the bottom of the > list." > -- Scrolling Cursor, What Not To Do > http://www.sqlite.org/cvstrac/wiki?p=ScrollingCursor > > Just saying...
This is already getting slightly off-topic wrt the original discussion on EXISTS/IN, so I allowed myself to change the subject. But this is another important matter I think, and I've already seen mention of server-side cursors in these threads. I have a question on SO http://stackoverflow.com/questions/14144408/memory-efficient-constant-and-speed-optimized-iteration-over-a-large-table-in about exactly that problem, it would be great to see server-side cursors and/or a smarter way to iterate make it into core. I hacked my procedure by I'm sure there are better ways. I'm decently versed in python and have come to learn django internals, but I am zero on database side so I'm finding it difficult to propose a real contribution (the best effort I could put together is in the SO question). If nudged, I can try and help. thanks! Stefano -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
