Add columns from input tables to table function returned relation type #14115
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kasiafi
force-pushed
the
389TFRelationType
branch
from
3945153 to
ddc6c81
Compare
kasiafi
force-pushed
the
389TFRelationType
branch
5 times, most recently
from
7d4b50e to
21228ef
Compare
kasiafi
force-pushed
the
389TFRelationType
branch
from
21228ef to
754e58a
Compare
martint
reviewed
Oct 12, 2022
kasiafi
force-pushed
the
389TFRelationType
branch
3 times, most recently
from
df7a3a5 to
a0e5db5
Compare
|
@martint I addressed your comment, and added comments in the code, as discussed offline. Please review. |
kasiafi
force-pushed
the
389TFRelationType
branch
from
a0e5db5 to
6e95fb1
Compare
martint
approved these changes
Oct 24, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is the final part of the analysis of a table function invocation with support for table and descriptor arguments.
This change is not meaningful to the user, as those types of arguments are not supported, and the query containing them fails in the planner.
No docs or release notes required.
based on #13653