[
https://issues.apache.org/jira/browse/CALCITE-5664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ZheHu updated CALCITE-5664:
---------------------------
Description:
After CALCITE-111, we now support CONVERT(charValue, srcCharsetName,
destCharsetName) that works on converting character sets.
CONVERT(charValue USING transcodingName) also fits the SQL standard, and MySQL
has implement it, which is the same as TRANSLATE(charValue USING
transcodingName)
For example:
* select convert('employ_id' using utf16) as alia from employee
* select translate('employ_id' using utf8) as alia from employee
Noted: Calcite already supports this from the parser.
was:
After CALCITE-111, we now support CONVERT(charValue, srcCharsetName,
destCharsetName) that works on converting character sets.
CONVERT(charValue USING transcodingName) also fits the SQL standard, and MySQL
has implement it. For example:
* select convert('employ_id' using utf16) as alia from employee
Noted: Calcite already supports this from the parser.
> Support CONVERT function with "USING" keyword
> ---------------------------------------------
>
> Key: CALCITE-5664
> URL: https://issues.apache.org/jira/browse/CALCITE-5664
> Project: Calcite
> Issue Type: Improvement
> Components: core
> Affects Versions: 1.34.0
> Reporter: ZheHu
> Assignee: ZheHu
> Priority: Minor
> Labels: pull-request-available
>
> After CALCITE-111, we now support CONVERT(charValue, srcCharsetName,
> destCharsetName) that works on converting character sets.
> CONVERT(charValue USING transcodingName) also fits the SQL standard, and
> MySQL has implement it, which is the same as TRANSLATE(charValue USING
> transcodingName)
> For example:
> * select convert('employ_id' using utf16) as alia from employee
> * select translate('employ_id' using utf8) as alia from employee
> Noted: Calcite already supports this from the parser.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
