You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@calcite.apache.org by "Josh Elser (JIRA)" <ji...@apache.org> on 2016/08/03 16:16:20 UTC

[jira] [Commented] (CALCITE-1335) ArrayImpl to return JDBC objects for method getArray()

    [ https://issues.apache.org/jira/browse/CALCITE-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15406143#comment-15406143 ] 

Josh Elser commented on CALCITE-1335:
-------------------------------------

In case you weren't aware, the support for Arrays in the Avatica wire protocol are also lacking. It's on my list to get around to CALCITE-1050

> ArrayImpl to return JDBC objects for method getArray()
> ------------------------------------------------------
>
>                 Key: CALCITE-1335
>                 URL: https://issues.apache.org/jira/browse/CALCITE-1335
>             Project: Calcite
>          Issue Type: Bug
>          Components: avatica
>    Affects Versions: avatica-1.8.0
>            Reporter: Maryann Xue
>
> Avatica uses Integer or Long representations for Date/Time/Timestamp objects, and similarly for Date/Time/Timestamp array objects. However, when calling getArray() method, the array implementation (class ArrayImpl) should decode from its internal representation and convert it into JDBC types before returning the objects to the client.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)