#11104: HAVING filter screws with extra() SQL parameter ordering
--------------------------------------+-------------------------------------
Reporter: miracle2k | Owner:
Status: new | Milestone:
Component: ORM aggregation | Version: SVN
Resolution: | Keywords:
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
--------------------------------------+-------------------------------------
Comment (by mpaolini):
I think all filters on annotated queryset should end up in HAVING clause,
not in WHERE
imagine you want to do something like:
{{{
SELECT * FROM blog group by location, rating having count(id) > 10 OR
rating >1
}}}
right now (r11199) you can ony add HAVING clauses using if you filter
using an aggregate. Does this make sense to you?
--
Ticket URL: <http://code.djangoproject.com/ticket/11104#comment:2>
Django <http://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 post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
