[
https://issues.apache.org/jira/browse/CALCITE-6730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17906569#comment-17906569
]
ZheHu commented on CALCITE-6730:
--------------------------------
Thanks for the reminder, and I suppose the summary should be changed to
"default character set".
BTW, I have one small question. Since we cannot distinguish
{code:java}
convert(string bytea, src_encoding name, dest_encoding name)
{code}
from
{code:java}
convert(string bytea, dest_encoding name, src_encoding name)
{code}
during the Parser.
Shall we change the parameter's order in OracleSqlDialect through unparsing?
> Add CONVERT function(enabled in Oracle library)
> -----------------------------------------------
>
> Key: CALCITE-6730
> URL: https://issues.apache.org/jira/browse/CALCITE-6730
> Project: Calcite
> Issue Type: Improvement
> Components: core
> Affects Versions: 1.38.0
> Reporter: ZheHu
> Assignee: ZheHu
> Priority: Major
>
> Unlike standard CONVERT function implemented in Calcite:
> {code:java}
> convert(string bytea, src_encoding name, dest_encoding name)
> {code}
> Oracle's [CONVERT
> |https://docs.oracle.com/en/database/oracle/oracle-database/19/nlspg/sql-and-plsql-programming-in-global-environment.html#GUID-7E4AA2C5-8CD7-4836-AA69-6C8E02594FAC]
> works like:
> {code:java}
> convert(string bytea, dest_encoding name[, src_encoding name])
> {code}
> If the 'src_encoding' parameter is not specified, then it defaults to the
> database character set.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
