[
https://issues.apache.org/jira/browse/CALCITE-2530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16604027#comment-16604027
]
Julian Hyde commented on CALCITE-2530:
--------------------------------------
Per the SQL standard, it should throw if the string does not have length 1. I
don't know where the Beam folks got their information.
I don't recall whether Calcite has a mechanism to throw an exception (with a
given SQL code 22027) at query run time from Java code that has been generated
to implement SQL. That is what is needed here.
> 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)
