#30188: Aggregate annotation, Case() - When(): AssertionError No exception
message
supplied
-------------------------------------+-------------------------------------
Reporter: Lukas Klement | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 2.1
(models, ORM) |
Severity: Normal | Resolution:
Keywords: query, aggregate, | Triage Stage: Accepted
case/when |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Simon Charette):
The assertion error is addressed by
https://github.com/django/django/pull/11062 but it unveiled another issue
regarding aggregation over annotations.
I managed to get it to work by adjusting the ''hacky''
`Query.rewrite_cols` function but then I noticed the subquery was
annotated twice which might hurt performance. I guess the suggested
approach at least works and the double annotation issue seems to be
generalized anyway. I suggest we open a following ticket to address the
`rewrite_cols` extra annotation issue and proceed with the current
approach for now.
--
Ticket URL: <https://code.djangoproject.com/ticket/30188#comment:18>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/070.2007064e5dda40b3b80db1aecff8342b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
