#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
-------------------------------------+-------------------------------------
Comment (by GitHub <noreply@…>):
In [changeset:"23b659402663dace32a04a0bf15dd13e5bfadc7e" 23b6594]:
{{{#!CommitTicketReference repository=""
revision="23b659402663dace32a04a0bf15dd13e5bfadc7e"
Fixed #36584, Refs #36149 -- Allowed subquery values against tuple in
lookup via ForeignObject.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36149#comment:8>
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/0107019962f98b56-09384b22-d7e7-47c2-ba24-cefd3eb68c9f-000000%40eu-central-1.amazonses.com.
