Add aliasing to create named tuples #32
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.
Our generated SQL casts anonymous tuples to named tuples at the very top:
The above fails starting in ClickHouse 24.7 due to a breaking change:
This manifests is a very weird way: when casting, we end up getting the default value for the data type, because we cannot fetch the correct column in the tuple.
Turns out, it's possible to alias fields when creating a named tuple, to set the names for the tuple: