#28175: __in query on parent model no longer works in 1.11
-------------------------------------+-------------------------------------
Reporter: Daniel Keller | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 1.11
(models, ORM) |
Severity: Release blocker | 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 GitHub <noreply@…>):
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"d66378a8b2d48d41b56ba3622189493e4edf9e5a" d66378a8]:
{{{
#!CommitTicketReference repository=""
revision="d66378a8b2d48d41b56ba3622189493e4edf9e5a"
Fixed #28175 -- Fixed __in lookups on a foreign key when using the foreign
key's parent model as the lookup value.
Thanks Simon Charette for review.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/28175#comment:6>
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/070.439d5db376931c1664fbac802205ffb4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
