Preserve the name of column after unnest #11193
Closed
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.
Motivation
Before #10883, we were able to do the following selection:
SELECT a.field1, a.field2 FROM UNNEST(...) t(a)
After the patch, this kind of query become impossible. The name of the fields becomes
_col0, _col1
. Column aliases is required in order to select the needed columns. We could rewrite it in this way:SELECT field1, field2 FROM UNNEST(...) t(field1, field2)
However, it is infeasible to use column aliases to refer to a row with a lot of fields. I think we should preserve the name of the columns so that we can refer to the column easily, as below:
What changes were proposed in this pull request
Before:
After: