You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Julian Hyde (JIRA)" <ji...@apache.org> on 2017/01/09 19:45:58 UTC

[jira] [Commented] (CALCITE-420) Add REPLACE character string function

    [ https://issues.apache.org/jira/browse/CALCITE-420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15812660#comment-15812660 ] 

Julian Hyde commented on CALCITE-420:
-------------------------------------

[~rictomm], The PR looks good as far as it goes. Can you please also update REFERENCE.md and add tests; see CALCITE-1557's additions to SqlOperatorBaseTest.

> Add REPLACE character string function
> -------------------------------------
>
>                 Key: CALCITE-420
>                 URL: https://issues.apache.org/jira/browse/CALCITE-420
>             Project: Calcite
>          Issue Type: Bug
>            Reporter: Julian Hyde
>            Assignee: Julian Hyde
>              Labels: newbie
>
> Oracle and MSSQL have a REPLACE function (see http://docs.oracle.com/cd/B19306_01/server.102/b14200/functions134.htm). It is not in the SQL standard, and in fact the standard has no equivalent function.
> Syntax:
> {code:sql}
> REPLACE(char, search_string [, replace_string])
> {code}
> REPLACE is not a reserved word. Therefore the implementation will need to add REPLACE to CommonNonReservedKeyWord() in the parser.
> Note that Drill and potentially other users of Optiq use REPLACE as part of CREATE OR REPLACE syntax. Careful not to break that.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)