#36648: "pk" exception when using first() on unordered queryset with aggregation
does not consider composite pk fields provided separately
-------------------------------------+-------------------------------------
Reporter: Jacob Walls | Owner: Jacob
| Walls
Type: Bug | Status: closed
Component: Database layer | Version: 5.2
(models, ORM) |
Severity: Release blocker | Resolution: fixed
Keywords: compositepk | 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 Jacob Walls <jacobtylerwalls@…>):
In [changeset:"8baee531d40cd6ee8b342dbcf2c7924d20694969" 8baee53]:
{{{#!CommitTicketReference repository=""
revision="8baee531d40cd6ee8b342dbcf2c7924d20694969"
[5.2.x] Fixed #36648, Refs #33772 -- Accounted for composite pks in
first()/last() when aggregating.
Backport of 02eed4f37879b2077496f86bb1378a076b981233 from main.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36648#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/01070199e44653a5-06a6612c-1ac2-427f-af1b-1d8a38988fe0-000000%40eu-central-1.amazonses.com.
