#32690: Q object __or__ appears to get all dunder related's default columns and
queryset raises ProgrammingError.
-------------------------------------+-------------------------------------
Reporter: allen-munsch | Owner: Simon
| Charette
Type: Bug | Status: closed
Component: Database layer | Version: 3.2
(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 Mariusz Felisiak <felisiak.mariusz@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"136ff592ad8aa8b7fa1e61435e5501cc98ce8573" 136ff592]:
{{{
#!CommitTicketReference repository=""
revision="136ff592ad8aa8b7fa1e61435e5501cc98ce8573"
Fixed #32690 -- Fixed __in lookup crash when combining with filtered
aggregates.
Having lookups group by subquery right-hand-sides is likely unnecessary
in the first place but relatively large amount of work would be needed
to achieve that such as making Lookup instances proper resolvable
expressions.
Regression in 35431298226165986ad07e91f9d3aca721ff38ec.
Thanks James A. Munsch for the report.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/32690#comment:9>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/070.b875cef35b3e7a66230a14cd177e0d8c%40djangoproject.com.
