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

fanluo updated CALCITE-6426:
----------------------------
    Description: 
When performing starrocks dialect conversion for cast (xxx as int) and cast 
(xxx as bigint), it defaults to using MySQL dialect,like this:

!image-2024-06-03-19-57-22-686.png|width=839,height=123!

while starlocks does not explicitly declare support for the signed data type. 
If conversion is performed according to the MySQL dialect by default, the 
execution result will exceed expectations when the data value exceeds the range 
[-2147483648,2147483647]

  was:
When performing starrocks dialect conversion for cast (xxx as int) and cast 
(xxx as bigint), it defaults to using MySQL dialect,like this:

!image-2024-06-03-19-57-22-686.png|width=839,height=123!

while starlocks does not explicitly declare support for the signed data type. 
If conversion is performed according to the MySQL dialect by default, the 
execution result will exceed expectations when the data value exceeds the range 
[-21474836482147483647]


> When performing starrocks dialect conversion for cast (xxx as int) and cast 
> (xxx as bigint), it defaults to using MySQL dialect
> -------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CALCITE-6426
>                 URL: https://issues.apache.org/jira/browse/CALCITE-6426
>             Project: Calcite
>          Issue Type: Bug
>    Affects Versions: 1.37.0
>            Reporter: fanluo
>            Priority: Major
>              Labels: pull-request-available
>         Attachments: image-2024-06-03-19-57-22-686.png
>
>
> When performing starrocks dialect conversion for cast (xxx as int) and cast 
> (xxx as bigint), it defaults to using MySQL dialect,like this:
> !image-2024-06-03-19-57-22-686.png|width=839,height=123!
> while starlocks does not explicitly declare support for the signed data type. 
> If conversion is performed according to the MySQL dialect by default, the 
> execution result will exceed expectations when the data value exceeds the 
> range [-2147483648,2147483647]



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

Reply via email to