On Jan 22, 2008 8:16 AM, code_berzerker <[EMAIL PROTECTED]> wrote: > this gives 5 Poll objects. I wonder if this is efficient way of > getting them? Does django get all rows first and then sort it and then > slice it to get only 5? Or is it optimized somehow. The question is if > its simplified for the tutorial and inefficient or this is the right > way to do it?
It's right. If you keep reading, you'll see (in tutorial part 4) a note which explains this: "Note all() is lazy It might look a little frightening to see Poll.objects.all() being used in a detail view which only needs one Poll object, but don't worry; Poll.objects.all() is actually a special object called a QuerySet, which is "lazy" and doesn't hit your database until it absolutely has to. By the time the database query happens, the object_detail generic view will have narrowed its scope down to a single object, so the eventual query will only select one row from the database. If you'd like to know more about how that works, The Django database API documentation explains the lazy nature of QuerySet objects." -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
