[
https://issues.apache.org/jira/browse/FLINK-9970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16593415#comment-16593415
]
ASF GitHub Bot commented on FLINK-9970:
---------------------------------------
yanghua commented on issue #6432: [FLINK-9970] [table] Add ASCII/CHR function
for table/sql API
URL: https://github.com/apache/flink/pull/6432#issuecomment-416175409
@fhueske I created
[FLINK-10222](https://issues.apache.org/jira/browse/FLINK-10222) to track this
issue. I recommend matching all suffixes exactly, which does not adversely
affect the semantics of suffix, but theoretically avoids conflicts with
function names prefixed by it, just like `ascii` and `asc`. Do you agree?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Add ASCII/CHR function for table/sql API
> ----------------------------------------
>
> Key: FLINK-9970
> URL: https://issues.apache.org/jira/browse/FLINK-9970
> Project: Flink
> Issue Type: Sub-task
> Components: Table API & SQL
> Reporter: vinoyang
> Assignee: vinoyang
> Priority: Minor
> Labels: pull-request-available
>
> for ASCII function :
> refer to :
> [https://dev.mysql.com/doc/refman/8.0/en/string-functions.html#function_ascii]
> for CHR function :
> This function convert ASCII code to a character,
> refer to : [https://doc.ispirer.com/sqlways/Output/SQLWays-1-071.html]
> Considering "CHAR" always is a keyword in many database, so we use "CHR"
> keyword.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
