On Tue, Jun 22, 2010 at 10:01 AM, Alex Gaynor <alex.gay...@gmail.com> wrote: > Hey all, > > This past week was mostly spent getting lookup's working (and > negation), that's gone fairly well. Well enough, in fact, that I > spent most of today getting some low hanging fruit working: namely > ordering, slicing, and values. In slicing we've come to an > interesting design decision. Attempting to do a LIMIT 0's equivilant > in MongoDB results in the full result set being returned, not a 0 item > result set, as SQL does. So the question is: do we emulate the SQL > (and CPython) behavior here, or do we simply write it off as a > platform specific issue. In this case the emulation happens to be > painless, efficient, and simple to implement, however in many other > cases it will not be.
Emulation seems like the right approach to me. From the end-user's perspective, you don't ever issue a LIMIT 0 -- you issue a query with slicing arguments that imply no results will be returned. I would expect nothing different under the MongoDB backend -- the internal hoops you need to jump through to make this happen are irrelevant. Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
