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 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 in the documentation that shows the usage of multiple aggregations.
On 5 Jan 2022, at 10:16 pm, Niccolò Mineo <niccol...@gmail.com> wrote:
I would be in favor of a real time information about the issue.
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-develop...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/1e17088d-dd5f-481e-94c7-2b4d2bcfa91dn%40googlegroups.com.