[
https://issues.apache.org/jira/browse/CALCITE-6923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17939239#comment-17939239
]
Julian Hyde commented on CALCITE-6923:
--------------------------------------
If the function has different behaviors on Postgres and BigQuery then we can’t
just fix the implementation. We need two different functions. (If we take this
course, the summary needs to be changed.)
> REGEXP_REPLACE backward references not working
> ----------------------------------------------
>
> Key: CALCITE-6923
> URL: https://issues.apache.org/jira/browse/CALCITE-6923
> Project: Calcite
> Issue Type: Bug
> Components: core
> Affects Versions: 1.38.0
> Reporter: Ulrich Kramer
> Priority: Minor
>
> REGEXP_REPLACE builtin function differs from Postgres/BigQuery
> The builtin function is using {{$1}} for backward reference. Postgres and
> [BigQuery|https://cloud.google.com/bigquery/docs/reference/standard-sql/string_functions#regexp_replace]
> are using {{\1}}.
> {code:SQL}
> SELECT REGEXP_REPLACE('abc','([bc]+)','$1','g')
> {code}
> produces {{abc}}. Running the same query against Postgres or BigQuery will
> return {{a$1}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
