[
https://issues.apache.org/jira/browse/CALCITE-6654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18030399#comment-18030399
]
Jeremy Osterhoudt edited comment on CALCITE-6654 at 10/16/25 3:50 PM:
----------------------------------------------------------------------
Looks like it used to set precision to 0 prior to 1.38.0 to the sqlType. I'll
play with a couple options, including setting it to PRECISION_NOT_SPECIFIED and
see what works out to re-enabling pre-1.38.0 functionality just for the JDBC
adapter.
was (Author: JIRAUSER311237):
Looks like it used to set precision to 0 prior to 1.38.0 to the sqlType. I'll
play with a couple options, including setting it for and see
PRECISION_NOT_SPECIFIED which works out to re-enabling pre-1.38.0 functionality
just for the JDBC adapter.
> Postgres NUMERIC type leads to "DECIMAL precision 0 must be between 1 and 19"
> -----------------------------------------------------------------------------
>
> Key: CALCITE-6654
> URL: https://issues.apache.org/jira/browse/CALCITE-6654
> Project: Calcite
> Issue Type: Bug
> Components: core
> Affects Versions: 1.38.0
> Reporter: Ulrich Kramer
> Priority: Major
>
> Tying to query a VIEW in Postgres, which has one column of type NUMERIC,
> leads to the error
> {noformat}
> DECIMAL precision 0 must be between 1 and 19 {noformat}
> The corresponding precision metadata column in postgres contains a NULL value.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
