[
https://issues.apache.org/jira/browse/CALCITE-3970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17101029#comment-17101029
]
Julian Hyde commented on CALCITE-3970:
--------------------------------------
I don't recall where {{CURSOR}} came from, or whether it is even in the
standard, but it seems that this use of {{TABLE}} is very similar to Calcite's
current use of {{CURSOR}}. So, how about allowing {{TABLE}} as an alternative
to {{CURSOR}}, and deprecating {{CURSOR}} with an eye to eventually removing it?
> Table-valued function TUMBLE uses non-standard syntax
> -----------------------------------------------------
>
> Key: CALCITE-3970
> URL: https://issues.apache.org/jira/browse/CALCITE-3970
> Project: Calcite
> Issue Type: Bug
> Components: core
> Affects Versions: 1.22.0
> Reporter: Viliam Durina
> Priority: Major
>
> The currently supported syntax is this:
> {code:java}
> SELECT * FROM TABLE(TUMBLE(TABLE my_table, ...
> {code}
> But the SQL standard specifies that {{my_table}} must be in parentheses, such
> as here:
> {code:java}
> SELECT * FROM TABLE(TUMBLE(TABLE(my_table), ...
> {code}
> The second syntax is currently rejected with:
> {code:none}
> Exception in thread "main" org.apache.calcite.sql.parser.SqlParseException:
> Encountered "(" at line 1, column 33.
> Was expecting one of:
> <BRACKET_QUOTED_IDENTIFIER> ...
> <QUOTED_IDENTIFIER> ...
> <BACK_QUOTED_IDENTIFIER> ...
> <IDENTIFIER> ...
> <UNICODE_QUOTED_IDENTIFIER> ...
> {code}
> I'm not sure if the currently supported syntax is optional, but I think it's
> not.
> I followed this document:
> [http://standards.iso.org/ittf/PubliclyAvailableStandards/c069776_ISO_IEC_TR_19075-7_2017.zip]
> The {{TABLE}} clause acts in both ways: (1) to convert a table value to a
> table object (when used in the {{FROM}} clause to convert the function
> result) and (2) to convert a table object to a table value (when used to
> convert arguments to a function).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
