#32152: Aggregation over subquery annotation GROUP BY produces wrong results
-------------------------------------+-------------------------------------
Reporter: Christian Klus | Owner: Christian
| Klus
Type: Bug | Status: closed
Component: Database layer | Version: 3.0
(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: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak <felisiak.mariusz@…>):
In [changeset:"b0a6798de59151163b94d1c0ccf0d010a3d46ac2" b0a6798d]:
{{{
#!CommitTicketReference repository=""
revision="b0a6798de59151163b94d1c0ccf0d010a3d46ac2"
[3.0.x] Fixed #32152 -- Fixed grouping by subquery aliases.
Regression in 42c08ee46539ef44f8658ebb1cbefb408e0d03fe.
Thanks Simon Charette for the review.
Backport of 4ac2d4fa42e1659f328c35b6b8d4761b3419c11a from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/32152#comment:11>
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 on the web visit
https://groups.google.com/d/msgid/django-updates/065.e9459ac3c2007522ac9df750ebd06943%40djangoproject.com.
