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/03/01 07:22:00 UTC

[jira] [Commented] (CALCITE-111) Support CONVERT function, for changing character sets

    [ https://issues.apache.org/jira/browse/CALCITE-111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17694884#comment-17694884 ] 

Julian Hyde commented on CALCITE-111:
-------------------------------------

[~VAE], I just reviewed, rebased and fixed up your PR. Sorry it took me so long. Please take a look at my [julianhyde/111-convert|https://github.com/julianhyde/calcite/tree/111-convert] dev branch and let me know whether you agree with my changes. 

> Support CONVERT function, for changing character sets
> -----------------------------------------------------
>
>                 Key: CALCITE-111
>                 URL: https://issues.apache.org/jira/browse/CALCITE-111
>             Project: Calcite
>          Issue Type: Improvement
>            Reporter: GitHub Import
>            Assignee: ZheHu
>            Priority: Major
>              Labels: github-import, pull-request-available
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Support the CONVERT function, to convert strings from one character set to another.
> CONVERT is defined in SQL:2011 as a feature called {{<character transliteration>}}. Here is an example:
> {code}
> SELECT * FROM emp WHERE CONVERT(name USING UTF16) = u&'\82f1\56fd'
> {code}
> The [MySQL site|https://dev.mysql.com/doc/refman/8.0/en/cast-functions.html#function_convert] has other examples.
> {noformat}
> ---------------- Imported from GitHub ----------------
> Url: https://github.com/julianhyde/optiq/issues/111
> Created by: [julianhyde|https://github.com/julianhyde]
> Labels: enhancement, 
> Created at: Tue Jan 14 03:40:53 CET 2014
> State: open
> {noformat}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)