You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@calcite.apache.org by "Julian Hyde (Jira)" <ji...@apache.org> on 2023/05/03 19:13:00 UTC

[jira] [Resolved] (CALCITE-5664) Support CONVERT function with "USING" keyword

     [ https://issues.apache.org/jira/browse/CALCITE-5664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Julian Hyde resolved CALCITE-5664.
----------------------------------
    Fix Version/s: 1.35.0
       Resolution: Fixed

Fixed in [a25f4a73|https://github.com/apache/calcite/commit/a25f4a733dac1526dbacf8a96dca5e21c5f14e84]; thanks for the PR, [~VAE]!

> 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
>             Fix For: 1.35.0
>
>
> 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)