#26925: ORM changes grouping when default ordering is set
-------------------------------------+-------------------------------------
Reporter: njoyard | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.8
(models, ORM) |
Severity: Normal | Resolution:
Keywords: aggregation | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by charettes):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
I'm tempted to close this as ''wontfix'' since this is a
[https://docs.djangoproject.com/en/1.9/topics/db/aggregation/#interaction-
with-default-ordering-or-order-by documented] caveat of aggregating over a
model with a default `ordering`.
Maybe we could add another warning to the `Meta.ordering` docs pointing to
aforementioned caveat as silently ignoring the ordering is not an option
at this point as it would be backward incompatible.
--
Ticket URL: <https://code.djangoproject.com/ticket/26925#comment:1>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.3ed51e6382bc89b4ce719849b2bbdfc2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
