#11305: Support for "Conditional Aggregates"
---------------------------------+-----------------------------------------
Reporter: bendavis78 | Owner: akaariai
Type: New feature | Status: new
Component: ORM aggregation | Version: 1.0
Severity: Normal | Resolution:
Keywords: | Triage Stage: Someday/Maybe
Has patch: 1 | Needs documentation: 1
Needs tests: 1 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
---------------------------------+-----------------------------------------
Changes (by akaariai):
* owner: => akaariai
Comment:
I have turned my mind on the -0. The approach is not the cleanest, but the
approach could be included as is (minor refactoring needed, though).
Later, when there is better support for custom aggregates and aggregates
that take parameters, we could use that framework to implement the
conditional aggregates. The user visible API would not change.
So, I will try to clean up the patch a bit. I hope there is enough
interest from core developers that we can push this forward. IMHO this is
very useful feature, and there seems to be others who think so, too.
This still needs documentation, more tests and then review(s). Helping by
testing and reviewing the patch is the way to get this included. Though
there is not much point until I have time to update the patch. I hope to
do it this weekend.
--
Ticket URL: <https://code.djangoproject.com/ticket/11305#comment:13>
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.
