Fix Trino transpilation of nullable single field ROW
generated from EXCLUDE
#46
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.
Issue #, if available:
union(string, null)
#44Description of changes:
ROW
type. When there is just one field within theROW
type, then we must know the type when constructing theROW
.union(string, null)
#44 comes from when we transpileEXCLUDE
and there is aROW
with a single fieldROW
when the field's type is aunion(<some single type>, null)
. New logic will remove thenull
from theunion
since Trino types are nullable by default.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.