#30158: Subquery expressions unnecessarily added to group by
-------------------------------------+-------------------------------------
Reporter: Jonny Fuller | Owner: Simon
Type: | Charette
Cleanup/optimization | Status: closed
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: subquery, group_by | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham <timograham@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"fb3f034f1c63160c0ff13c609acd01c18be12f80" fb3f034f]:
{{{
#!CommitTicketReference repository=""
revision="fb3f034f1c63160c0ff13c609acd01c18be12f80"
Fixed #30158 -- Avoided unnecessary subquery group by on aggregation.
Subquery annotations can be omitted from the GROUP BY clause on
aggregation
as long as they are not explicitly grouped against.
Thanks Jonny Fuller for the report.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/30158#comment:16>
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.3175522c99144379eadf038bde5afd91%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.