#14357: Prevent inappropriate order-based grouping on values+annotate queries
-------------------------------------+-------------------------------------
Reporter: Martin Chase | Owner: (none)
Type: Bug | Status: closed
Component: Database layer | Version:
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: 3.1 | Triage Stage:
| Someday/Maybe
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Adam Sołtysik):
For anyone surprised, just like me, that `Meta.ordering` still breaks
aggregation queries in Django 3.1 and 3.2, despite what the documentation
says [https://docs.djangoproject.com/en/4.0/releases/3.1/#features-
removed-in-3-1 here] and
[https://docs.djangoproject.com/en/4.0/releases/2.2/#model-meta-ordering-
will-no-longer-affect-group-by-queries here], it seems that this was
finally fixed in #32546 in Django 4.0. Possibly the documentation should
be updated to reflect the actual version when the change was implemented,
as there seems to be nothing about it in the
[https://docs.djangoproject.com/en/4.0/releases/4.0/ release notes for
4.0]. Or maybe the change should be backported to reflect the
documentation.
--
Ticket URL: <https://code.djangoproject.com/ticket/14357#comment:27>
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/070.465a6b5531604228e4666195dcd6a308%40djangoproject.com.
