On Sun, 2007-06-10 at 15:45 -0400, Forest Bond wrote: > Hi, > > Using the sqlite3 backend, any slice operation on a QuerySet for which the > slice > does not start at 0, a list is returned instead of a QuerySet, and the slice > is > not performed in the database, but in Python. > > Is this expected behavior? The sqlite3 docs indicate that offsets can be > given, > so I see no reason this shouldn't be performed at the DB level.
I'm unable to repeat this behaviour. Whenever I construct a QuerySet and slice it, the LIMIT/OFFSET bits get added. The only time the slicing is done in Python is where I have already accessed the results of the QuerySet (so it has been cached). In those cases, Django knows not to do another round-trip to the database. Do you have a short example that reliably demonstrates the problem? Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
