[
https://issues.apache.org/jira/browse/CALCITE-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16868979#comment-16868979
]
Julian Hyde commented on CALCITE-3135:
--------------------------------------
What do you think should be the limits on the DECIMAL data type? What does the
SQL standard say?
(What java.math.BigDecimal is capable of is not pertinent. It is just an
implementation, and implementation can be changed.)
> Calcite decimal literal validation
> ----------------------------------
>
> Key: CALCITE-3135
> URL: https://issues.apache.org/jira/browse/CALCITE-3135
> Project: Calcite
> Issue Type: Bug
> Components: core
> Reporter: Praveen Kumar Desabandu
> Priority: Minor
>
> Hi Team,
> Thanks for the great product. I had a question while using the framework.
> I am not sure why we restrict decimal literals to 64 bit precision here -
> [https://github.com/apache/calcite/blob/master/core/src/main/java/org/apache/calcite/sql/validate/SqlValidatorImpl.java#L2952]
> BigDecimal is unbounded precision, so can someone please explain why we
> restrict literals to fit in long values?
> Thx.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
