[
https://issues.apache.org/jira/browse/CALCITE-5241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17582622#comment-17582622
]
Julian Hyde commented on CALCITE-5241:
--------------------------------------
* While '\{fn char ...\}' is in the JDBC standard, 'CHAR' is not in the SQL
standard. 'CHAR(65)' is not valid in Postgres or Oracle, for example. Maybe it
should be in {{SqlLibraryOperators}} (enabled for dialects such as MySQL) but
not {{SqlStdOperatorTable}}.
* More tests needed. Negative numbers, null, values between 128 and 255, 0.
Test the JDBC function separately from the CHAR function.
* Do you plan to implement the CHR function in this change? Oracle has it.
> Implement CHAR function
> -----------------------
>
> Key: CALCITE-5241
> URL: https://issues.apache.org/jira/browse/CALCITE-5241
> Project: Calcite
> Issue Type: Wish
> Components: core
> Reporter: pengfei.zhan
> Assignee: Jiajun Xie
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Implement the {{CHAR\(n)}} function and the \{fn CHAR(string)\} JDBC function.
> Spark and hive support `char\(n\)`, however, calcite doesn't support it. Is
> there any message I missed?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
