#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
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak <felisiak.mariusz@…>):
In [changeset:"3d734c09ff0138441dfe0a59010435871d17950f" 3d734c0]:
{{{
#!CommitTicketReference repository=""
revision="3d734c09ff0138441dfe0a59010435871d17950f"
Refs #33992 -- Refactored subquery grouping logic.
This required moving the combined queries slicing logic to the compiler
in order to allow Query.exists() to be called at expression resolving
time.
It allowed for Query.exists() to be called at Exists() initialization
time and thus ensured that get_group_by_cols() was operating on the
terminal representation of the query that only has a single column
selected.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/33992#comment:7>
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/01070183ad2554fb-b6f6160f-d1b5-4ed0-8815-17af3a6e099f-000000%40eu-central-1.amazonses.com.
