#29542: Annotated field created by subquery, referenced inside of F() generates
invalid SQL
-------------------------------------+-------------------------------------
Reporter: Joey Wilhelm | Owner: felixxm
Type: Bug | Status: closed
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by felixxm):
* status: assigned => closed
* resolution: => fixed
Comment:
In
[https://github.com/django/django/commit/dd3b4707198f17557fdd9fe7a6fd9025b23dcaf3
dd3b470]:
Fixed #29542 -- Fixed invalid SQL if a Subquery from the HAVING clause is
used in the GROUP BY clause.
Thanks Tim Graham for the review.
--
Ticket URL: <https://code.djangoproject.com/ticket/29542#comment:8>
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/069.de147525f26d5f612b42a4207da5ce59%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
