[
https://issues.apache.org/jira/browse/CALCITE-2459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16590823#comment-16590823
]
Julian Hyde commented on CALCITE-2459:
--------------------------------------
Decode is a perfect example - it has a totally different meaning in Oracle and
PostgreSQL. So, it would not make sense to enable both at the same time.
Best thing might be to place functions in "packages", and someone could choose
to run SQL with "standard,oracle" as their default packages. They could still
use functions in other packages, by qualifying with package name, e.g.
"postgres.decode(..., 'base64')".
The [fun connect-string
parameter|https://calcite.apache.org/apidocs/org/apache/calcite/config/CalciteConnectionProperty.html#FUN]
is a step in that direction.
> Add implementation of From_Base64 to SqlFunctions
> -------------------------------------------------
>
> Key: CALCITE-2459
> URL: https://issues.apache.org/jira/browse/CALCITE-2459
> Project: Calcite
> Issue Type: Improvement
> Components: core
> Reporter: vinoyang
> Assignee: Julian Hyde
> Priority: Minor
>
> refer to mysql FROM_BASE64 function :
> [https://dev.mysql.com/doc/refman/5.6/en/string-functions.html#function_from-base64]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
