Hello,
There's a ticket <https://code.djangoproject.com/ticket/10060> opened 13 years ago explaining a problem with combining multiple aggregations with annotate(). And the solution appears to be documenting <https://docs.djangoproject.com/en/4.0/topics/db/aggregation/#combining-multiple-aggregations> the problem. But for people skimming through the documentation, the message might not be noticeable. Showing the problem in a warning message could help draw attention better. It's used here <https://docs.djangoproject.com/en/4.0/ref/settings/#static-root> and in other places in the doc. In addition to documenting the problem, raising an exception might prevent developers from spending hours trying to debug their code. While the problem is recognized, there's an example <https://docs.djangoproject.com/en/4.0/topics/db/aggregation/#joins-and-aggregates>in the documentation that shows the usage of multiple aggregations. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/09a8b1df-414e-4dd1-a202-0c6833b50c91n%40googlegroups.com.
