#24268: Remove Query.having
-------------------------------------+-------------------------------------
Reporter: akaariai | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Database | Version: master
layer (models, ORM) |
Severity: Normal | Keywords:
Triage Stage: | Has patch: 1
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
Instead of Query.having and Query.where we could instead use Query.where
only, and then split that to where and having parts in the compiler.
The main reason for doing the split in compiler is that we gain a bit
simpler Query class without any significant complications to the where
class.
There are other cases, too, where such a split would be needed. For
example, window aggregates can't be filtered on the same query level. So,
`qs.filter(row_num__lte=10)` would need to be splitted into an outer
query's where clause.
--
Ticket URL: <https://code.djangoproject.com/ticket/24268>
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/051.ba19ed489000c6db769d8aeb4ff05ce2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
