#17144: Excessive GROUP BY clauses during aggregations.
----------------------------------+------------------------------------
Reporter: christian_oudard | Owner: nobody
Type: Bug | Status: new
Component: ORM aggregation | Version: 1.3
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------+------------------------------------
Comment (by sbussetti):
This is a larger issue that merely the double inclusion of the pk. For
any query using annotation, ALL fields from query.select are listed in the
groupby clause, even when it would only be appropriate for the grouping to
only occur on the primary key. For mysql this basically guarantees that
all annotated queries will use the worst possible "Using temporary; Using
filesort" method to evaluate the sql.
--
Ticket URL: <https://code.djangoproject.com/ticket/17144#comment:3>
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
