[
https://issues.apache.org/jira/browse/CALCITE-6699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
xiaochen.zhou updated CALCITE-6699:
-----------------------------------
Description:
When performing starrocks dialect conversion for {{{}varchar{}}}, it defaults
to using MySQL dialect，MySQL doesn't have a VARCHAR type, only CHAR,So during
StarRocks dialect conversion, VARCHAR will also be converted to CHAR
Since StarRocks supports the VARCHAR type, we should modify the StarRocks
dialect.
!image-2025-01-06-13-35-11-888.png|width=348,height=151!
https://docs.starrocks.io/docs/sql-reference/data-types/string-type/VARCHAR/
was:When performing starrocks dialect conversion for {{{}varchar{}}}, it
defaults to using MySQL dialect，MySQL doesn't have a VARCHAR type, only CHAR,So
during StarRocks dialect conversion, VARCHAR will also be converted to CHAR
> Invalid unparse for Varchar in StarRocksDialect
> -----------------------------------------------
>
> Key: CALCITE-6699
> URL: https://issues.apache.org/jira/browse/CALCITE-6699
> Project: Calcite
> Issue Type: Bug
> Affects Versions: 1.38.0
> Reporter: xiaochen.zhou
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.39.0
>
> Attachments: image-2025-01-06-13-35-11-888.png
>
>
> When performing starrocks dialect conversion for {{{}varchar{}}}, it defaults
> to using MySQL dialect，MySQL doesn't have a VARCHAR type, only CHAR,So during
> StarRocks dialect conversion, VARCHAR will also be converted to CHAR
> Since StarRocks supports the VARCHAR type, we should modify the StarRocks
> dialect.
>
> !image-2025-01-06-13-35-11-888.png|width=348,height=151!
>
> https://docs.starrocks.io/docs/sql-reference/data-types/string-type/VARCHAR/
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
