#36181: Composite primary key fields cannot use __in lookup with explicit
Subquery
-------------------------------------+-------------------------------------
Reporter: Jacob Walls | 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
-------------------------------------+-------------------------------------
Comment (by Sarah Boyce <42296566+sarahboyce@…>):
In [changeset:"771c250b106f8f4beda42c104c60498ed568b5e2" 771c250]:
{{{#!CommitTicketReference repository=""
revision="771c250b106f8f4beda42c104c60498ed568b5e2"
[5.2.x] Fixed #36181 -- Allowed Subquery usage in __in lookups against
composite pks.
Thanks Jacob Walls for the report.
Backport of 8561100425876bde3be4b2a22324655f74ff9609 from main.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36181#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/01070194fe6f24b0-82b49ed8-95dd-46c2-95e6-6d7a097cb5a2-000000%40eu-central-1.amazonses.com.
