On 20 Nov, 01:35, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> On Wed, 2008-11-19 at 00:34 -0800, Nicola Murino wrote:
>
> [...]
>
> > I would like to do something similar to this:
>
> > def recursive(n,o1):
> > nodes=Nodes.objects.select_related().filter(sublivello_di=n)
> > o1=o1.filter(node=n)
> > .....
>
> > for o in o1: #no db access I passed the full queryset so why
> > access the db?
>
> You are saying that you want to access each object "o" inside the
> queryset. That is, you want Python to assign to "o" each element from
> the queryset in turn. So it has to actually access the elements of the
> queryset to get the items out. Naturally, database access is required
> for that.
>
> I really don't see what you are expecting to happen here. If you want to
> work with the individual elements of a queryset, the queryset needs to
> be populated, which means the database has to be accessed. That
> shouldn't be surprising.
>
> Regards,
> Malcolm
Sorry Malcom, my explaination is not clear:
I want populate a queryset for example with all table elements, for
example:
nodes=Nodes.objects.select_related().all()
I want this query is performed so for example i do
print nodes
next I want to do nodes.filter(...=...)
when I filter another query is done, why? the queryset already have
all the needed info, so why hit the database?
I hope my explaination is enough clear,
regards
Nicola
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
