#30158: Subquery Expressions Incorrectly Added to Group by
-------------------------------------+-------------------------------------
Reporter: JonnyWaffles | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution: invalid
Keywords: subquery, group_by | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 1 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by JonnyWaffles):
Replying to [comment:6 Simon Charette]:
> I just ran the full suite with the `get_group_by_cols` override detailed
and it worked fine, this case is simply untested.
>
> Jonny, would you be interested in submitting a Github PR with the
changes suggested above with the addition of a regression test to make
sure the `GROUP BY` doesn't occur? I'd be happy to offer assistance like I
did for #30099 in https://github.com/django/django/pull/10846.
Sure thing Simon. I just need to figure out how to write a generic test
case...
--
Ticket URL: <https://code.djangoproject.com/ticket/30158#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/070.7471d38daacb6d0659fd408d620bccb6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
