#35744: Composite query support doesn't report nested correlated queries
external
references
-------------------------------------+-------------------------------------
Reporter: Simon | Owner: (none)
Charette |
Type: Bug | Status: assigned
Component: Database | Version: 4.1
layer (models, ORM) |
Severity: Normal | Keywords:
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
As I came to discover [https://forum.djangoproject.com/t/filtering-model-
instances-m2m-field-to-exactly-match-another-m2m-field-or-list/34533/6
trying to help someone on the forum] the support for correlated subqueries
(aka `OuterRef`) in composite queries (`union`, `intersection`,
`difference`) added in #29338 fails to re-point external references on
relabeling (an operation performed on subquery pushdown to prevent table
name collisions) causing nested outer query references to be orphaned.
--
Ticket URL: <https://code.djangoproject.com/ticket/35744>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/01070191d455d6db-1a37192b-b357-486e-85b8-f55987158710-000000%40eu-central-1.amazonses.com.
