I think I'm OK with `list_aggregates` because it implies a terminal 
queryset method which really restricts the members used to create that 
aggregation (the GROUP BY). Adding aggregates to existing list_display 
would require something *else* to refine the group by using `values()`.

If list_aggregates is a useful feature, then this sounds like an 
appropriate way to implement that. Regular annotations could be added and 
processed within list_display, provided list_display was modified to accept 
expressions (either aggregates or regular annotations) in tuple form for 
alias support.

list_aggregates -> queryset.aggregate()
list_display -> queryset.annotate(annotations).values()

Does that make sense?

You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
For more options, visit https://groups.google.com/d/optout.

Reply via email to