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 2020/12/07 22:34:00 UTC
[jira] [Comment Edited] (CALCITE-4427) Make SUBSTRING operator
comply with ISO standard SQL
[ https://issues.apache.org/jira/browse/CALCITE-4427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17245545#comment-17245545 ]
Julian Hyde edited comment on CALCITE-4427 at 12/7/20, 10:33 PM:
-----------------------------------------------------------------
[~jamesstarr], The desired behavior is that SUBSTR will give the semantics of database {{xxx}} based on your connection's {{fun=xxx}} setting.
The JDBC adapter will have to be clever in generating SQL to make sure that that happens. (Meaning: We have some bugs to fix.)
was (Author: julianhyde):
[~jamesstarr], The desired behavior is that SUBSTR will give the semantics of database \{{xxx}} based on your connection's {{fun=xxx}} setting.
The JDBC adapter will have to be clever in generating SQL to make sure that that happens.
> Make SUBSTRING operator comply with ISO standard SQL
> ----------------------------------------------------
>
> Key: CALCITE-4427
> URL: https://issues.apache.org/jira/browse/CALCITE-4427
> Project: Calcite
> Issue Type: Bug
> Reporter: Julian Hyde
> Priority: Major
>
> Make {{SUBSTRING}} operator comply with ISO standard SQL. It currently complies with BigQuery standard SQL, which gives different behavior when start is negative. See discussion in CALCITE-4408.
> Add an option to get the BigQuery behavior, for those who want it.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)