[
https://issues.apache.org/jira/browse/CALCITE-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17817548#comment-17817548
]
Julian Hyde commented on CALCITE-6265:
--------------------------------------
I think the bug is in Avatica - or at any rate, Avatica is the most logical
place to fix it. If a parameter has type {{{}INTEGER{}}}, and a user calls
{{{}PreparedStatement.setShort{}}}, it is Avatica's job to coerce that value to
a {{{}java.lang.Integer{}}}.
It is analogous to – in fact, the reverse of – when someone calls
{{ResultSet.getInt}} on a column that is of type {{{}SMALLINT{}}}. I believe
that Avatica does that conversion already.
> Cannot provide different numeric type as placeholder
> ----------------------------------------------------
>
> Key: CALCITE-6265
> URL: https://issues.apache.org/jira/browse/CALCITE-6265
> Project: Calcite
> Issue Type: Bug
> Components: core
> Reporter: Tim Nieradzik
> Assignee: Tim Nieradzik
> Priority: Major
> Labels: pull-request-available
>
> The _empid_ column is of type {_}INT{_}. When providing a _short_ value as a
> placeholder, a _ClassCastException_ is thrown.
> *Test case:*
> {{ final String sql =}}
> {{ "select \"empid\" from \"hr\".\"emps\" where \"empid\" in (?,
> ?)";}}{{ CalciteAssert.hr()}}
> {{ .query(sql)}}
> {{ .consumesPreparedStatement(p -> {}}
> {{ p.setShort(1, (short) 100);}}
> {{ p.setShort(2, (short) 110);}}
> {{ })}}
> {{ .returnsUnordered("empid=100", "empid=110");}}
> *Stack trace:*
> {{java.lang.ClassCastException: class java.lang.Short cannot be cast to class
> java.lang.Integer (java.lang.Short and java.lang.Integer are in module
> java.base of loader 'bootstrap')}}
> {{ at Baz$1$1.moveNext(Unknown Source)}}
> {{ at
> org.apache.calcite.linq4j.Linq4j$EnumeratorIterator.<init>(Linq4j.java:679)}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
