#14030: Use F() objects in aggregates(), annotates() and values()
-------------------------------------+-------------------------------------
Reporter: delfick | Owner: smeatonj
Type: New feature | Status: assigned
Component: Database layer | Version: master
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: aggregate, annotate | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by bendavis78):
I was about to post to django-dev about this when I discovered it was
already being worked on. Very pleased about this. Having an API for
commonly used SQL expressions, available anywhere in the query, will
really open up the door for flexible queries. I think this could even pave
the way to deprecating `.extra()` :-)
I've posted some use cases that I'm hoping will be covered by this:
https://gist.github.com/bendavis78/865611a9e36c0897cb00 . Would any of
these be difficult to implement with the addition of this patch?
--
Ticket URL: <https://code.djangoproject.com/ticket/14030#comment:43>
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.25dbfd371db4805f6b4a3a04e7dc18a1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
