#29539: Cannot use Aggregation function in Model.Meta.ordering
-------------------------------------+-------------------------------------
Reporter: wilhelmhb | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 2.0
(models, ORM) |
Severity: Normal | Resolution: wontfix
Keywords: ordering, query | Triage Stage: Accepted
expression, aggregation function |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham):
* status: new => closed
* resolution: => wontfix
Comment:
From Simon on the pull request:
I think this feature would be hard to get right for the rare case where
it's useful. It also go against our stance on trying to disconnect
Meta.ordering from aggregation (#14357) as this PR demonstrates. I'd be in
favour of won't fixing the ticket as well for these reasons. It feels
incoherent with the ongoing deprecation motivated by observed user
confusion over the years from the interactions between these two features.
--
Ticket URL: <https://code.djangoproject.com/ticket/29539#comment:6>
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/067.20a64489c71e8af5e7dd2bbb7a216fbd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
