Changes between Initial Version and Version 2 of Ticket #35744


Ignore:
Timestamp:
Sep 8, 2024, 8:42:11 PM (3 months ago)
Author:
Simon Charette
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #35744

    • Property Has patch set
    • Property Summary Composite query support doesn't report nested correlated queries external references → Combine query support doesn't repoint nested external references

  • Ticket #35744 – Description

    initial v2  
    1 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.
     1As 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 combined 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.
Back to Top