#36149: Composite primary key subquery lookup prevent usage or specify fields
and
are not implemented for exact
-------------------------------------+-------------------------------------
Reporter: Simon Charette | Owner: Simon
| Charette
Type: Bug | Status: closed
Component: Database layer | Version: 5.2
(models, ORM) |
Severity: Release blocker | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Sarah Boyce <42296566+sarahboyce@…>):
* resolution: => fixed
* status: assigned => closed
Comment:
In [changeset:"41239fe34d64e801212dccaa4585e4802d0fac68" 41239fe3]:
{{{#!CommitTicketReference repository=""
revision="41239fe34d64e801212dccaa4585e4802d0fac68"
Fixed #36149 -- Allowed subquery values against tuple exact and in
lookups.
Non-tuple exact and in lookups have specialized logic for subqueries that
can
be adapted to properly assign select mask if unspecified and ensure the
number
of involved members are matching on both side of the operator.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36149#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 view this discussion visit
https://groups.google.com/d/msgid/django-updates/01070194f40d99f5-402801c0-c17e-44fa-983e-57f00a71f9b7-000000%40eu-central-1.amazonses.com.
