Boris Smus wrote:
> On Mar 12, 6:56 am, Tim Chase <[EMAIL PROTECTED]>
> wrote:>
>> cs.filter(
>> Q(default_recipe__ingredients__ingredient__id=3) |
>> Q(default_recipe__ingredients__ingredient__id=1)
>> )
>
> Just to clarify, I was trying to get AND functionality, as Kon
On Mar 12, 6:56 am, Tim Chase <[EMAIL PROTECTED]>
wrote:>
> cs.filter(
> Q(default_recipe__ingredients__ingredient__id=3) |
> Q(default_recipe__ingredients__ingredient__id=1)
> )
Just to clarify, I was trying to get AND functionality, as Konstantin
suggested. I also tried
>
> >[56]:cs.filter(default_recipe__ingredients__ingredient__id=3).filter(default_recipe__ingredients__ingredient__id=1)
>> Out[56]:[]
> This would map to a Query that looks like this "... WHERE id=3 AND
> id=1". that would most certainly return no results.
Unless those ingredients were qbits
Hello,
please allow me to disagree. the first two queries in the original
post return result sets which overlap. but they combined return the
empty set. this is the problem.
konstantin
On Mar 12, 9:13 am, Atilla <[EMAIL PROTECTED]> wrote:
> On 12/03/07, Boris Smus <[EMAIL PROTECTED]> wrote:
>
On 12/03/07, Boris Smus <[EMAIL PROTECTED]> wrote:
>[56]:cs.filter(default_recipe__ingredients__ingredient__id=3).filter(default_recipe__ingredients__ingredient__id=1)
> Out[56]:[]
This would map to a Query that looks like this "... WHERE id=3 AND
id=1". that would most certainly return no resul
Dear Djangoites,
I ran into problems trying to chain multiple filters on a QuerySet
with models in a many-to-many relationship. Based on the word from
irc, and from perusal of the mailing list, it seems that this is a
known issue. But the last ML post on it (that I could find) dates back
to 2006-
6 matches
Mail list logo
