[
https://issues.apache.org/jira/browse/CALCITE-1050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15975210#comment-15975210
]
Josh Elser commented on CALCITE-1050:
-------------------------------------
{quote}
As far as I can tell, a JDBC driver is safe to assume that every Array it sees
is one of its own. If a user creates class MyArrayImpl implements Array and
passes it to PreparedStatement.setArray they will get an error.
As a user, if I want to create an array, I must call Connection.createArrayOf.
{quote}
That makes sense to me. Something else to fix up down in Phoenix land.
Should I make the leap to say that you agree with me that TypedValue is doing
the wrong thing (by not creating an Array object for the JDBC form)?
> Avatica can't serialize java.sql.Array
> --------------------------------------
>
> Key: CALCITE-1050
> URL: https://issues.apache.org/jira/browse/CALCITE-1050
> Project: Calcite
> Issue Type: Improvement
> Components: avatica
> Affects Versions: 1.5.0
> Reporter: Lukas Lalinsky
> Assignee: Josh Elser
> Fix For: avatica-1.10.0
>
>
> As far as I can see, there is no way to serialize arrays in the Avatica RPC.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
