#23589: Django 1.7 filter Q m2m bug
-------------------------------------+-------------------------------------
Reporter: Grafumbly | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 1.7
(models, ORM) | Resolution: invalid
Severity: Normal | Triage Stage:
Keywords: | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by akaariai):
* status: new => closed
* resolution: => invalid
Comment:
The interpretation of the query is that PrimaryObject must have a *single*
relatedobject row for which (someparam=True AND NOT someparam=False).
Obviously if someparam=True, then someparam is also not False for that
row. The 1.7 results seem correct to me. (See
https://docs.djangoproject.com/en/1.7/topics/db/queries/#spanning-multi-
valued-relationships for how Django handles filters to multivalued
relationships).
I believe you will get correct results by using
`.filter(Q(relatedobject__someparam=True)).filter(~Q(relatedobject__someparam=False))`.
--
Ticket URL: <https://code.djangoproject.com/ticket/23589#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.78b1441d71a0e1cdd0cc39678bb46bd2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
