Fix panic when CTE references column from another CTE's source table #4130
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes a panic when a UNION ALL query uses multiple CTEs where one CTE
references a column that exists in another CTE's source table but not
in its own.
Example that panicked:
The issue was that CTEs were added to
outer_query_refsfor table lookup(allowing
FROM cte1inside another CTE), but this also made their columnsavailable for resolution. Now CTE columns are only accessible when the CTE
is explicitly in the FROM clause.