[
https://issues.apache.org/jira/browse/CALCITE-2211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16411855#comment-16411855
]
Eyal Segal commented on CALCITE-2211:
-------------------------------------
You are correct. I don't think that MySql is the issue here but how JDBC
creates the objects based on the column type due to the "unsigned".
Unsigned BIGINT can bring up to 2^64-1 positive values, were regular long
provides 2^64 positive and negative values, so in JDBC they had to use
BigInteger to represent unsigned BIGINT properly.
> Type of BigInteger should be BIGINT
> -----------------------------------
>
> Key: CALCITE-2211
> URL: https://issues.apache.org/jira/browse/CALCITE-2211
> Project: Calcite
> Issue Type: Bug
> Affects Versions: 1.15.0
> Reporter: Eyal Segal
> Assignee: Julian Hyde
> Priority: Major
>
> Vertica DB returns BigInteger values as BigInteger. It seems thatÂ
> JavaToSqlTypeConversionRules doesn't support mapping between BigInteger to
> BIGINT.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
