#30739: OuterRef in exclude() or ~Q() uses wrong model.
-------------------------------------+-------------------------------------
Reporter: Oskar Persson | Owner: Simon
| Charette
Type: Bug | Status: closed
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak <felisiak.mariusz@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"13a8884a08342817094cc6287c7ae346100a297d" 13a8884a]:
{{{
#!CommitTicketReference repository=""
revision="13a8884a08342817094cc6287c7ae346100a297d"
Fixed #30739 -- Fixed exclusion of multi-valued lookup against outer rhs.
OuterRef right hand sides have to be nested, just like F rhs have to,
during the subquery pushdown split_exclude performs to ensure they are
resolved against the outer query aliases.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/30739#comment:4>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/070.6eba63f9330a9023bafb639d968c9a86%40djangoproject.com.
