#30665: Add DISTINCT handling for widely-supported aggregates
-------------------------------------+-------------------------------------
Reporter: Étienne | Owner: Étienne Beaulé
Beaulé |
Type: New | Status: assigned
feature |
Component: Database | Version: 2.2
layer (models, ORM) |
Severity: Normal | Keywords:
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
As an extension of #28658, aggregates should be supported for other
general aggregates such as `Avg` and `Sum`. Before 2.2, these aggregations
just ignored the parameter, but now throw an exception.
This change would just involve setting these classes as allowing
`DISTINCT`, and could also be applied to `Min` and `Max` (although
pointless).
--
Ticket URL: <https://code.djangoproject.com/ticket/30665>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/051.b5a11f2b26a64dedc98c60ba1b27fadc%40djangoproject.com.
