#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
-------------------------------------+-------------------------------------
Changes (by Jacob Walls <jacobtylerwalls@…>):
* resolution: => fixed
* status: assigned => closed
Comment:
In [changeset:"02eed4f37879b2077496f86bb1378a076b981233" 02eed4f]:
{{{#!CommitTicketReference repository=""
revision="02eed4f37879b2077496f86bb1378a076b981233"
Fixed #36648, Refs #33772 -- Accounted for composite pks in first()/last()
when aggregating.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36648#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/01070199e4446c15-741076e2-468e-4e44-877e-8e866270c176-000000%40eu-central-1.amazonses.com.
