I think Jacob is correct, both choices result in the entire result set being read into memory, however #2 leaves the users code database agnostic.
On Jul 14, 7:21 pm, "Jacob Kaplan-Moss" <[EMAIL PROTECTED]> wrote: > On Mon, Jul 14, 2008 at 7:13 PM, Malcolm Tredinnick > > <[EMAIL PROTECTED]> wrote: > > (2) For SQLite *only*, we go back to the pre-queryset-refactor > > behaviour: all results are read in immediately upon accessing the > > queryset. > > I'd prefer this -- ``list(qs)`` essentially ties user code to their > choice of databases. If you upgrade later, you end up with inefficient > code that you don't need any more. If possible, database limitations > shouldn't leak down into user code. > > Jacob --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
