You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Julian Hyde (Jira)" <ji...@apache.org> on 2022/04/25 16:32:00 UTC
[jira] [Updated] (CALCITE-4861) Optimization of chained CAST calls can lead to unexpected behavior
[ https://issues.apache.org/jira/browse/CALCITE-4861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julian Hyde updated CALCITE-4861:
---------------------------------
Summary: Optimization of chained CAST calls can lead to unexpected behavior (was: Optimisation of chained cast calls can lead to unexpected behaviour)
> Optimization of chained CAST calls can lead to unexpected behavior
> ------------------------------------------------------------------
>
> Key: CALCITE-4861
> URL: https://issues.apache.org/jira/browse/CALCITE-4861
> Project: Calcite
> Issue Type: Bug
> Components: core
> Reporter: Marios Trivyzas
> Priority: Minor
> Labels: pull-request-available
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> Simplification of Cast chained calls can lead to unexpected behaviour:
> {code}CAST(CAST(CAST(123456 AS TINYINT) AS INT) AS BIGINT){code}
> is simplified to
> {code}
> CAST(123456 AS BIGINT){code}
> and returns *123456* with *BIGINT* data type, where the first inner cast as TINYINT should already fail because the value is out of range.
> For example, for PostgreSQL:
> {noformat}
> postgres=# select 123456::smallint::int::bigint;
> ERROR: smallint out of range{noformat}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)