feat: Allow use of table and column aliases for table functions returning unknown types #2156
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.
At the moment, when a table function returns a type that isn't a known table, it's excluded from the output columns completely. This makes it impossible to use
unnest()
orunnest() WITH ORDINALITY
with a table alias (#1205, #1596).This PR allows constructs such as
and
I haven't attempted to solve this problem in general - it will only work for a table alias with column alias(es), and data types are
any
, necessitating casts. This seems like a good first step, at least.Fixes #1205