On Sun, 2007-07-01 at 06:31 +0000, Davide.D wrote:
> >If you don't want to do that, just construct one queryset for each model
> >and then join the results together in Python. You get to decide which
> >trade-off you prefer: more queries and simpler code (appropriate if you
> >have only a few models and/or not many results) or fewer queries and
> >more complex Python code.
> 
> Queryset is not a list?

I think you know the answer to your own question. :-)

They can be used as iterators, but are not list subclasses (in order to
save resources).

You might want to read:
http://www.djangoproject.com/documentation/db-api/#when-querysets-are-evaluated 
for example.

Regards,
Malcolm

-- 
How many of you believe in telekinesis? Raise my hand... 
http://www.pointy-stick.com/blog/


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to