[
https://issues.apache.org/jira/browse/CALCITE-991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15027442#comment-15027442
]
Julian Hyde commented on CALCITE-991:
-------------------------------------
bq. SqlUserDefinedFunction: The existing hierarchy was a little confusing to
me. TableUserDefinedFunction extends it. We can change this.
I don't like to give the end user a choice of many constructors. So maybe the
one used (only) by SqlUserDefinedTableFunction could be protected or
package-protected so that no one is tempted to use it?
> Create separate SqlFunctionCategory values for table functions and macros
> -------------------------------------------------------------------------
>
> Key: CALCITE-991
> URL: https://issues.apache.org/jira/browse/CALCITE-991
> Project: Calcite
> Issue Type: Improvement
> Reporter: Julien Le Dem
> Assignee: Julian Hyde
>
> This avoids trying to apply a table function in a context where it does not
> apply or a regular function where a table function is needed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
