#24747: Allow transforms in order_by
-------------------------------------+-------------------------------------
Reporter: sparkyb | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by jarshwah):
I had a quick look at this a few weeks back, and while I didn't actually
implement any of it, I think I found the place where the work would need
to be done.
https://github.com/jarshwah/django/commit/0522ccd1b4f7867f662de238ec9437dbed72f0d9
I would hope to get this done before django 1.10, but my time lately has
been totally consumed by day-job and family.
As far as distinct queries go, distinct would have to support F()
expressions internally for this patch to have any effect there. I'm not
even certain that this would be enough, because I think you'd still need
to have the field__transform in the select list. I haven't played with
this enough to know though.
--
Ticket URL: <https://code.djangoproject.com/ticket/24747#comment:4>
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.97919c3ebe4a746dbec569f4427d433e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
