[
https://issues.apache.org/jira/browse/CALCITE-2846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16778550#comment-16778550
]
Julian Hyde commented on CALCITE-2846:
--------------------------------------
Regarding annotations. We clearly need to make it reasonably easy to add a
particular function to a particular flavor. E.g. we want to add the NVL
function to the Teradata flavor. But I don't want to make it *too* easy. I
would like to see a code change where someone made that decision to add NVL to
Teradata. I don't want functions to appear in flavors because someone forgot to
exclude them.
By all means create sets of functions, if it makes things easier to manage
(e.g. LTRIM and RTRIM could be in the same set)
> Document Oracle-specific functions, such as NVL and LTRIM, in the SQL
> reference
> -------------------------------------------------------------------------------
>
> Key: CALCITE-2846
> URL: https://issues.apache.org/jira/browse/CALCITE-2846
> Project: Calcite
> Issue Type: Improvement
> Components: site
> Reporter: Julian Hyde
> Assignee: Hongze Zhang
> Priority: Major
> Labels: documentation
>
> Document Oracle-specific functions (DECODE, NVL, LTRIM, RTRIM, SUBSTR,
> GREATEST, LEAST) in the [SQL
> reference|https://calcite.apache.org/docs/reference.html].
> Same goes for MySQL-specific functions (e.g. JSON_TYPE).
> I don't think we should have separate lists of Oracle-specific functions and
> MySQL-specific functions. Because quite a few functions appear in more than
> one place. Better, I think, to have a concise annotation against each
> function which tables it occurs in.
> The current list of tables is standard, oracle, spatial, mysql. Perhaps also
> indicate whether a function is an extension to the SQL standard but still
> occurs in Calcite's default table.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
