[
https://issues.apache.org/jira/browse/CALCITE-2599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16788730#comment-16788730
]
Andrei Sereda commented on CALCITE-2599:
----------------------------------------
[~julianhyde] it is not very clear what to do for extended ASCII charset (128 -
255) and UNICODE. Should we explicitly state that {{ASCII}} works only for
basic (printable?) ASCII chars ? Throw exception if not ?
[UNICODE|https://docs.microsoft.com/en-us/sql/t-sql/functions/ascii-transact-sql?view=sql-server-2017]
looks more generic. ASCII and UNICODE / UTF8 are identical for basic charset 0
- 127.
> Support ASCII(string) in SqlFunctions
> -------------------------------------
>
> Key: CALCITE-2599
> URL: https://issues.apache.org/jira/browse/CALCITE-2599
> Project: Calcite
> Issue Type: Improvement
> Components: core
> Reporter: TANG Wen-hui
> Priority: Major
> Labels: pull-request-available
> Time Spent: 2h 40m
> Remaining Estimate: 0h
>
> {fn ASCII(string)}- Convert a single-character string to the corresponding
> ASCII code, an integer between 0 and 255
> [https://calcite.apache.org/docs/reference.html]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
