You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "ZheHu (Jira)" <ji...@apache.org> on 2023/04/19 03:49: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=17713881#comment-17713881 ] 

ZheHu commented on CALCITE-111:
-------------------------------

[~julianhyde] Thanks for your review. I've already seen your changes, which all look good to me! You can merge this from your branch if it's OK.

> 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
>             Fix For: 1.35.0
>
>          Time Spent: 20m
>  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)