[
https://issues.apache.org/jira/browse/CALCITE-2530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17914105#comment-17914105
]
Julian Hyde edited comment on CALCITE-2530 at 3/10/25 8:09 PM:
---------------------------------------------------------------
This case is fixed via CALCITE-2571 (commit
[8f14945|https://github.com/apache/calcite/commit/8f14945461b3c20cba3f2d794a6ac950b7687da9#diff-cb3257551f96f6523e9c4464d9359b21b0408ccfb7315955f97a59b45546bc1c]).
So I mark it as duplicate and fixed.
was (Author: vae):
This case is fixed via
[CALCITE-2571|https://github.com/apache/calcite/commit/8f14945461b3c20cba3f2d794a6ac950b7687da9#diff-cb3257551f96f6523e9c4464d9359b21b0408ccfb7315955f97a59b45546bc1c].
So I mark it as duplicate and fixed.
> 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:
> 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
(v8.20.10#820010)
