On Jun 20, 12:07 pm, Christoph Neuroth <[EMAIL PROTECTED]>
wrote:
> Theres still a problem with this :(
> Request.objects.filter(parameters=1, parameters=2)
> is not the same as
> Request.objects.filter(parameters=2, parameters=1)
Yes. Sorry for suggesting that query earlier. Please see below.
>
> However the following two queries seem to be working as expected now
> (i'm pretty sure they didnt work when I tried it the last time - or I
> had a typo or something):
It's quite possible that you were in a pre-qsrf trunk previously. The
following only works (and is documented) after the qsrf merge to
trunk.
> models.Request.objects.filter(parameters=1).filter(parameters=2)
> models.Request.objects.filter(parameters=2).filter(parameters=1)
>
> The Q&Q thingie still doesnt work though, not sure if this i a bug or
> me misunderstanding something.
It doesn't look like the Q&Q is documented to work for filtering via a
multi-valued relationship.
Take the doc here:
http://www.djangoproject.com/documentation/db-api/#spanning-multi-valued-relationships
It mentions the two cases:
filter(x__j=b, x__k=c)
filter(x__j=b).filter(x__k=c)
Where x is a multi-val relationship.
Judging by the second example in the doc above, it seems
Request.objects.filter(parameters=1).filter(parameters=2) is the way
to find all Request objects that have both RequestParameters. In
particular, this excerpt in that doc looks consistent with that:
Blog.objects.filter(entry__headline__contains='Lennon').filter(
entry__pub_date=datetime.date.today())
"In this second example, the first filter restricted the queryset to
all those blogs linked to that particular type of entry. The second
filter restricted the set of blogs *further* to those that are also
linked to the second type of entry."
Sorry I suggested Request.objects.filter(parameters=2, parameters=1)
earlier. Reading the above docs again, that seems meaningless since
all conditions inside that filter are applied to a *single* instance
of the target relation. So, it makes no sense to try to match to a
target RequestParameter whose id is both 1 and 2! It seems that in
such a case, the DB API only considers the last parameters=X.
-RD
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
