[
https://issues.apache.org/jira/browse/CALCITE-2510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16597343#comment-16597343
]
Sergey Nuyanzin commented on CALCITE-2510:
------------------------------------------
There is also {{CHAR}} [1]/{{NCHAR}} [2] in Microsoft SQL Server
but in Microsoft SQL Server {{CHAR}} supports only {{0..255}} as input
otherwise it returns {{null}}
Does it make sense to have MicrosoftSqlOperatorTable as well?
btw I found such comparison of {{CHR}}/{{CHAR}} between different DBs [3]
[1]
[https://docs.microsoft.com/en-us/sql/t-sql/functions/char-transact-sql?view=sql-server-2017]
[2]
[https://docs.microsoft.com/en-us/sql/t-sql/functions/nchar-transact-sql?view=sql-server-2017]
[3] [https://doc.ispirer.com/sqlways/Output/SQLWays-1-071.html]
> CHR support
> -----------
>
> Key: CALCITE-2510
> URL: https://issues.apache.org/jira/browse/CALCITE-2510
> Project: Calcite
> Issue Type: Task
> Components: core
> Reporter: Sergey Tsvetkov
> Assignee: Julian Hyde
> Priority: Major
>
> Adding CHR() function support, available in Oracle & PostgreSql
> [https://docs.oracle.com/cd/B19306_01/server.102/b14200/functions019.htm]
> [https://www.postgresql.org/docs/9.4/static/functions-string.html]
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
