You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Hongze Zhang (JIRA)" <ji...@apache.org> on 2018/09/05 03:07:00 UTC
[jira] [Updated] (CALCITE-2530) Reasonable behavior of TRIM
function when the length of trim character is not 1(one)
[ https://issues.apache.org/jira/browse/CALCITE-2530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hongze Zhang updated CALCITE-2530:
----------------------------------
Description:
Calcite's TRIM function takes the first character of <trim character> string to trim the <trim source>, whereas SQL standard suggests to report a "trim error" when the length of <trim character> is not 1.
I am not sure if this could be treated as an issue(since the calcite's way might has better availability), until I found this:
https://issues.apache.org/jira/browse/BEAM-4704
It seems user could be sometimes confused with the behavior of TRIM function in Calcite.
was:
Calcite's TRIM function takes the first character of <trim character> string to trim the <trim source>, whereas SQL standard suggests to report a "trim error" when the length of <trim character> is not 1.
I am not sure if this could be treated as an issue(since the calcite's way might has better availability), until I found this:
[https://issues.apache.org/jira/browse/BEAM-4704|https://issues.apache.org/jira/browse/BEAM-4704]
It seems user could be sometimes confused with the behavior of TRIM function.
> Reasonable behavior of TRIM function when the length of trim character is not 1(one)
> ------------------------------------------------------------------------------------
>
> Key: CALCITE-2530
> URL: https://issues.apache.org/jira/browse/CALCITE-2530
> Project: Calcite
> Issue Type: Improvement
> Components: core
> Reporter: Hongze Zhang
> Assignee: Julian Hyde
> Priority: Minor
>
> Calcite's TRIM function takes the first character of <trim character> string to trim the <trim source>, whereas SQL standard suggests to report a "trim error" when the length of <trim character> is not 1.
> I am not sure if this could be treated as an issue(since the calcite's way might has better availability), until I found this:
> https://issues.apache.org/jira/browse/BEAM-4704
> It seems user could be sometimes confused with the behavior of TRIM function in Calcite.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)