Analyzer: identifier resolution in parent scopes#66143
Conversation
|
This is an automated comment for commit 57a3b91 with description of existing statuses. It's updated for the latest CI running ❌ Click here to open a full report in a separate page
Successful checks
|
d07fb46 to
e23c981
Compare
…e-in-parent-scope
…e-in-parent-scope
…e-in-parent-scope
Cherry pick #66143 to 25.1: Analyzer: identifier resolution in parent scopes
Cherry pick #66143 to 24.12: Analyzer: identifier resolution in parent scopes
|
Backporting has a risk of breaking customers' queries, do we have to do it? |
|
This PR has fixed many queries. Even without taking this into account, I still see backporting as necessary because we want to be able to backport other fixes in the future. |
|
From the list of cherry-pick references, I guess that this is missed from 24.10.x for some reason? |
|
@ei-grad We backport fixes only to LTS and the two last releases. That's why a cherry-pick to 24.10 was not created. Anyway, this fix was not backported to any previous version because it has too many conflicts, and resolving them takes a lot of effort and produces risks. |
Changelog category (leave one):
Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):
Fix identifier resolution from parent scopes. Allow the use of aliases to expressions in the WITH clause.
Fixes #58994.
Fixes #62946.
Fixes #63239.
Fixes #65233.
Fixes #71659.
Fixes #71828.
Fixes #68749.
Documentation entry for user-facing changes
CI Settings (Only check the boxes if you know what you are doing):