#33992: QuerySet.annotate() with subquery and aggregation crashes.
-------------------------------------+-------------------------------------
Reporter: Fernando Flores | Owner: Simon
Villaça | Charette
Type: Bug | Status: closed
Component: Database layer | Version: 4.1
(models, ORM) |
Severity: Release blocker | Resolution: fixed
Keywords: database, orm, | Triage Stage: Ready for
aggregation | checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak <felisiak.mariusz@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"e0f14d83898ee7d0d3180eb96214d8fcdf82cc1d" e0f14d8]:
{{{
#!CommitTicketReference repository=""
revision="e0f14d83898ee7d0d3180eb96214d8fcdf82cc1d"
[4.1.x] Fixed #33992 -- Fixed queryset crash when aggregating over a group
containing Exists.
A more in-depth solution is likely to make sure that we always GROUP BY
selected annotations or revisit how we use Query.exists() in the Exists
expression but that requires extra work that isn't suitable for a
backport.
Regression in e5a92d400acb4ca6a8e1375d1ab8121f2c7220be.
Thanks Fernando Flores Villaça for the report.
Backport of 32536b1324e98768dd892980408a8c6b26c23fd9 from main
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/33992#comment:5>
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/010701831bbbbb4f-afa00aac-75aa-404f-a58e-92196342838e-000000%40eu-central-1.amazonses.com.
