Support REPLACE SQL alias syntax
#7368
Merged
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.
Which issue does this PR close?
Closes #7367.
Rationale for this change
There are 2 different REPLACE usages in some other platforms: One of them is like:
which already works successfully, and the second one is like:
for more examples: https://cloud.google.com/bigquery/docs/reference/standard-sql/query-syntax#select_replace
which is parsed and put into
WildcardAdditionalOptions, but not evaluated. This PR completes the second version of REPLACE usage.What changes are included in this PR?
After expanding wildcards, replace option in the
SelectItemis checked. If it is Some, the corresponding expression is found and replaced with the new expression, but the name of that column is kept the same, by providing an alias as the original column name.Are these changes tested?
Yes, with .slt tests
Are there any user-facing changes?