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 2019/11/21 02:08:00 UTC

[jira] [Commented] (CALCITE-3522) sql validator limits decimal and long have the same precision, so the unscaled value of a decimal must fit into a long

    [ https://issues.apache.org/jira/browse/CALCITE-3522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16978908#comment-16978908 ] 

Julian Hyde commented on CALCITE-3522:
--------------------------------------

Are you talking about SQL types or Java types? Please be absolutely clear. Use upper-case for SQL types.

> sql validator limits decimal and long have the same precision, so the unscaled value of a decimal must fit into a long
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: CALCITE-3522
>                 URL: https://issues.apache.org/jira/browse/CALCITE-3522
>             Project: Calcite
>          Issue Type: Test
>          Components: core
>    Affects Versions: 1.18.0
>            Reporter: shuchangbo
>            Priority: Minor
>         Attachments: code.png
>
>
> [https://github.com/apache/calcite/blob/master/core/src/main/java/org/apache/calcite/sql/validate/SqlValidatorImpl.java#L2983]
> for example:
> create table tbl(f1 double),
> f1 stores a double's max value. (1.7976931348623157E308)
> long max value isĀ 9223372036854775807.
> select * from table where f1=value, if value is greater than long max, sqlvalidator will throw out of range exception.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)