#32546: Meta.ordering fields must not be included in GROUP BY clause
-------------------------------------+-------------------------------------
Reporter: Yuri | Owner: nobody
Konotopov |
Type: Bug | Status: new
Component: Database | Version: 3.1
layer (models, ORM) |
Severity: Normal | Keywords:
Triage Stage: | Has patch: 1
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
This continues (closed) ![1] ticket.
I beleave it was not properly fixed in commit [0ddb4ebf].
While commit [0ddb4ebf] removes ORDER BY when Meta.ordering is used it
still does populates GROUP BY with Meta.ordering fields thus leads to
wrong aggregation.
PR with test case was added at ![2].
[1] https://code.djangoproject.com/ticket/14357
[2] https://github.com/django/django/pull/14122
--
Ticket URL: <https://code.djangoproject.com/ticket/32546>
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/051.8ec44552c8517978f78ff0e18242d067%40djangoproject.com.
