#14030: Use F() objects in aggregates(), annotates() and values()
-------------------------------------+-------------------------------------
Reporter: delfick | Owner: nate_b
Type: New feature | Status: assigned
Component: Database layer | Version:
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: aggregate, annotate | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 1
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by smeatonj):
I'm wondering if there's been any traction on this ticket? It appeared
like akaariai was looking into it, but after rebasing it hasn't been
touched. I can't find a GSOC 2013 proposal linked to this ticket, so I'm
unsure if the last update resulted in anything either. This is a ticket
I'm deeply interested in, and wouldn't mind investing some time into it
myself.
Would it be better to pick up the current branch and work on some of the
issues that have been raised ( F() <-> SQLEvaluator ) etc? Or would it
perhaps be a better idea to tackle this from the current master, and start
anew? I guess I'm looking for a little direction before jumping into it.
--
Ticket URL: <https://code.djangoproject.com/ticket/14030#comment:30>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.c9fe714381d4462f49fd0811d88b0b4a%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
