Fix qualified column resolution for multiple JOINs with USING#95157
Merged
Fix qualified column resolution for multiple JOINs with USING#95157
Conversation
Contributor
|
Workflow [PR], commit [4047a5d] Summary: ❌
|
Fix types after change in analyzer. Added plus function to trigger logical error in case type is different from resolved funciton argument.
yariks5s
approved these changes
Jan 28, 2026
This was referenced Feb 2, 2026
Merged
Merged
Merged
Merged
clickhouse-gh bot
added a commit
that referenced
this pull request
Feb 2, 2026
Backport #95157 to 26.1: Fix qualified column resolution for multiple JOINs with USING
clickhouse-gh bot
added a commit
that referenced
this pull request
Feb 2, 2026
Backport #95157 to 25.11: Fix qualified column resolution for multiple JOINs with USING
vdimir
added a commit
that referenced
this pull request
Feb 3, 2026
Backport #95157 to 25.12: Fix qualified column resolution for multiple JOINs with USING
clickhouse-gh bot
added a commit
that referenced
this pull request
Feb 3, 2026
Backport #95157 to 25.8: Fix qualified column resolution for multiple JOINs with USING
vdimir
added a commit
that referenced
this pull request
Feb 5, 2026
Backport #95157 to 25.3: Fix qualified column resolution for multiple JOINs with USING
1 task
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Changelog category (leave one):
Changelog entry (a user-readable short description of the changes that goes into CHANGELOG.md):
USINGclause. Previously, subsequent joins incorrectly updated types of underlying source columns to a common supertype even when the column was not involved in that join (e.g., inSELECT t2.a FROM t1 LEFT JOIN t2 USING (a) LEFT JOIN t3 USING (a), thet2.acolumn is only used by the first join, so its type should be the supertype oft1.aandt2.a, excludingt3.a). This could lead to logical errors or crashes when functions expected different column types than what actually appeared in the execution plan.Ref #91738