#36210: Support exact lookups where lhs is CompositePrimaryKey and rhs is
Subquery
-------------------------------------+-------------------------------------
Reporter: Jacob Walls | Owner: Jacob
| Walls
Type: New feature | Status: closed
Component: Database layer | Version: 5.2
(models, ORM) |
Severity: Normal | 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:"181e3bd71c0f578a1214523be1f7969393d98892" 181e3bd7]:
{{{#!CommitTicketReference repository=""
revision="181e3bd71c0f578a1214523be1f7969393d98892"
Refs #36210 -- Corrected output_field comparison in
Subquery.resolve_expression().
Regression in fd569dd45bf0746378faf7f65172497f21ed27f0.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36210#comment:13>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/01070198983904bc-01b76c86-c441-4d99-8e06-ae6c16953113-000000%40eu-central-1.amazonses.com.
