#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):
Can, I guess we could somehow but I feel like we'd need a more elegant
solution than that.
Note that the double annotation issue doesn't only happen for subqueries,
you might have noticed that the `company_id` which is first annotated as
`Col0` gets annotated as `__col0` as well. This makes me believe we might
need to do it for `Col` instances as well?
--
Ticket URL: <https://code.djangoproject.com/ticket/30188#comment:20>
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.c93ceb044c4c4a5191f3461dfec94acc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
