[
https://issues.apache.org/jira/browse/CALCITE-2530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Hyde 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: 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
It seems user could be sometimes confused with the behavior of TRIM function in
Calcite.
> TRIM function does not throw exception 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: Bug
> Components: core
> Reporter: Hongze Zhang
> Priority: Minor
> Fix For: 1.18.0
>
>
> 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: BEAM-4704
> It seems user could be sometimes confused with the behavior of TRIM function
> in Calcite.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
