Skip to content

Analyze table function invocation in the context of a query#13653

Merged
kasiafi merged 3 commits intotrinodb:masterfrom
kasiafi:383TFRelationType
Oct 13, 2022
Merged

Analyze table function invocation in the context of a query#13653
kasiafi merged 3 commits intotrinodb:masterfrom
kasiafi:383TFRelationType

Conversation

@kasiafi
Copy link
Copy Markdown
Member

@kasiafi kasiafi commented Aug 12, 2022

No release notes needed.
Docs: the limitations on TF usage should be documented. The documentation is not included in this PR.

Based on #13602 and #13649

@cla-bot cla-bot bot added the cla-signed label Aug 12, 2022
@kasiafi kasiafi force-pushed the 383TFRelationType branch from fcc1239 to 9ad3215 Compare August 22, 2022 09:56
@github-actions github-actions bot added the docs label Aug 22, 2022
@kasiafi kasiafi force-pushed the 383TFRelationType branch 3 times, most recently from 609acaa to adea14e Compare September 12, 2022 09:51
@kasiafi kasiafi force-pushed the 383TFRelationType branch 5 times, most recently from a850ca2 to 1e8016a Compare October 1, 2022 15:00
@kasiafi kasiafi requested a review from martint October 3, 2022 11:26
Table sample or MATCH_RECOGNIZE should not be applied
to a polymorphic table function invocation.

Per SQL standard, relation alias is required for a polymorphic
table function with the GENERIC TABLE or static returned type,
and it is not allowed for table function with ONLY PASS THROUGH
returned type. We only enforce the latter rule.
@kasiafi
Copy link
Copy Markdown
Member Author

kasiafi commented Oct 12, 2022

@martint I applied your comments. Please review.

@kasiafi kasiafi requested a review from martint October 12, 2022 15:51
@kasiafi kasiafi merged commit c4bd83e into trinodb:master Oct 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

2 participants