[
https://issues.apache.org/jira/browse/CALCITE-2761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16732102#comment-16732102
]
Stamatis Zampetakis commented on CALCITE-2761:
----------------------------------------------
OK, I undestand better. However, I have a few questions/clarifications.
The change that you propose is to remove NVL from OracleSqlOperatorTable and
add it to SqlStdOperatorTable. Is that correct?
What does this refactoring bring in terms of new functionality?
What are the implications of this change for databases that do not support the
NVL function (e.g., Postgres)?
> ADD NVL function to SQL standard
> --------------------------------
>
> Key: CALCITE-2761
> URL: https://issues.apache.org/jira/browse/CALCITE-2761
> Project: Calcite
> Issue Type: Improvement
> Reporter: Stuti Gupta
> Assignee: Julian Hyde
> Priority: Major
>
> Teradata, Oracle, and Netezza have NVL function. It is not there in SQL
> standard. So adding it to SqlStdOperatorTable.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
