[
https://issues.apache.org/jira/browse/CALCITE-1115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Hyde resolved CALCITE-1115.
----------------------------------
Resolution: Fixed
Fix Version/s: (was: next)
1.8.0
I reviewed the PR and it looks good -- thanks! Fixed in
http://git-wip-us.apache.org/repos/asf/calcite/commit/4e33eedc.
I made a couple of changes in
http://git-wip-us.apache.org/repos/asf/calcite/commit/1be4056b. I moved the
function to OracleSqlOperatorTable, since it is not a standard SQL function.
(It is in Oracle and PostgreSQL but not in MySQL, for instance.) I also added
more validator tests, and changed the parser a bit.
> Add support for translate (expession, from_string, to_string)
> -------------------------------------------------------------
>
> Key: CALCITE-1115
> URL: https://issues.apache.org/jira/browse/CALCITE-1115
> Project: Calcite
> Issue Type: Improvement
> Affects Versions: 1.7.0
> Reporter: Arina Ielchiieva
> Assignee: Julian Hyde
> Fix For: 1.8.0
>
>
> Calcite follows the standard SQL reference.
> SQL reference, ISO/IEC 9075-2:2011(E), section 6.30
> <character transliteration> ::=
> TRANSLATE <left paren> <character value expression>
> USING <transliteration name> <right paren>
> Need to add support for translate (expession, from_string, to_string)
> alternative syntax.
> Ex: Add the Oracle-style TRANSLATE function to SqlStdOperatorTable
> (call it say TRANSLATE3, since it has 3 parameters)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
