[
https://issues.apache.org/jira/browse/ARROW-3904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16704037#comment-16704037
]
Wes McKinney edited comment on ARROW-3904 at 11/29/18 11:42 PM:
----------------------------------------------------------------
In PostgreSQL it seems to be configurable
https://www.postgresql.org/docs/10/datatype-numeric.html#DATATYPE-NUMERIC-DECIMAL
Parquet supports precision 1 through 38
(https://github.com/apache/parquet-format/blob/master/LogicalTypes.md#decimal).
It seems scale is limited to be between 0 and 38. So that seems like a
reasonable constraint for now
was (Author: wesmckinn):
In PostgreSQL it seems to be configurable
> [C++/Python] Validate scale and precision of decimal128 type
> ------------------------------------------------------------
>
> Key: ARROW-3904
> URL: https://issues.apache.org/jira/browse/ARROW-3904
> Project: Apache Arrow
> Issue Type: Improvement
> Components: C++, Python
> Reporter: Krisztian Szucs
> Priority: Major
>
> Do We have a specification for it?
> Currently I can create `pa.decimal128(-2147483648, 2147483647)`, which seems
> wrong.
> References:
> -
> https://docs.microsoft.com/en-us/sql/t-sql/data-types/precision-scale-and-length-transact-sql?view=sql-server-2017
> -
> https://docs.oracle.com/cd/B28359_01/server.111/b28318/datatype.htm#CNCPT1832
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
