[ https://issues.apache.org/jira/browse/CALCITE-2846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16823488#comment-16823488 ]
Julian Hyde commented on CALCITE-2846: -------------------------------------- [~stutigupta], Any progress on this? I'd love to get this into 1.20. There are quite a few issues (e.g. JSON_xxx functions) blocked on this. If it helps, we could split this into two tasks: 1. re-organize SqlOperatorTable, 2. re-organize reference.md. Let me know. > 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 > 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)