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

Posted to issues@calcite.apache.org by "Danny Chan (JIRA)" <ji...@apache.org> on 2019/07/29 02:25:00 UTC

[jira] [Comment Edited] (CALCITE-3212) Derive equivalent decimal type for integer and bigint

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

Danny Chan edited comment on CALCITE-3212 at 7/29/19 2:24 AM:
--------------------------------------------------------------

Thanks [~praveenbingo], does this behavior belongs to the SQL standard ? I found for MYSQL is the behavior you proposed.

I think the equivalence is mainly used for type cast, i.e. cast(int as decimal(10, 0)) when we need a decimal operand but actually it is an integer. I'm curious about what is your needs ?


was (Author: danny0405):
Thanks [~praveenbingo], does this behavior belongs to the SQL standard ? I found for MYSQL is the behavior you proposed.

I think the equivalence is mainly used for type cast, i.e. cast(int as decimal(10, 0)) when we need a decimal operand but actually it is an integer. I'm curious about what you needs are ?

> Derive equivalent decimal type for integer and bigint
> -----------------------------------------------------
>
>                 Key: CALCITE-3212
>                 URL: https://issues.apache.org/jira/browse/CALCITE-3212
>             Project: Calcite
>          Issue Type: Improvement
>            Reporter: Praveen Kumar Desabandu
>            Priority: Major
>
> Currently int and bigint literal  types default to 10,0 and 19,0 precision
> Allow clients to interpret them according to their values for e.g. a smallint, tinyint, int and bigint.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)