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

Posted to issues@calcite.apache.org by "Mihai Budiu (Jira)" <ji...@apache.org> on 2025/09/05 06:56:00 UTC

[jira] [Resolved] (CALCITE-7069) Invalid unparse for INT UNSIGNED and BIGINT UNSIGNED in MysqlSqlDialect

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

Mihai Budiu resolved CALCITE-7069.
----------------------------------
    Fix Version/s: 1.41.0
       Resolution: Fixed

Fixed in https://github.com/apache/calcite/commit/182b90955d00f52227a520e58d4e3e042e4da5d3
Thank you for the contribution [~VAE]
Thank you for the reviews [~xuzifu666][~nobigo]



> Invalid unparse for INT UNSIGNED and BIGINT UNSIGNED  in MysqlSqlDialect
> ------------------------------------------------------------------------
>
>                 Key: CALCITE-7069
>                 URL: https://issues.apache.org/jira/browse/CALCITE-7069
>             Project: Calcite
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.40.0
>            Reporter: ZheHu
>            Assignee: ZheHu
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: 1.41.0
>
>
> After CALCITE-1466, we support UNSIGNED INT and UNSIGNED BITINT types, however, in MySQL, cast(1 as INT UNSIGNED) or cast(1 as BIGINT UNSIGNED) is not legal, we should convert it to forms like cast(1 as UNSIGNED).



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