Opened 17 years ago
Closed 17 years ago
#7176 closed (wontfix)
HAVING clauses are not generated
| Reported by: | Jonathan Buchanan | Owned by: | nobody |
|---|---|---|---|
| Component: | Core (Other) | Version: | dev |
| Severity: | Keywords: | ||
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
django.db.models.sql.query.Query has a "having" attribute (a list) which isn't used outside of the init and clone methods - should this result in a HAVING clause being generated whenever a GROUP BY clause is being generated?
Note:
See TracTickets
for help on using tickets.
GROUP BY and HAVING are included in the Query class for completeness; there isn't really a way to use them at the moment unless you are hand crafting queries. Fully utilizing these pieces of Query is part of a much bigger problem - implementing aggregates in Django's ORM (See ticket #3566). This is the subject of a GSOC project this year.