#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:"2cc90728defa891332fe3894b6a8fd7c56bcd7c3" 2cc9072]:
{{{#!CommitTicketReference repository=""
revision="2cc90728defa891332fe3894b6a8fd7c56bcd7c3"
[6.0.x] Refs #36648 -- Removed hardcoded pk in CompositePKAggregateTests.
Backport of bee64561a6e8cd22995c2b1254bab66dae892a6d from main.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36648#comment:10>
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/01070199eb1f7f95-301ed541-9ea2-439f-b75a-76ca9e2eaf82-000000%40eu-central-1.amazonses.com.
