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

Posted to issues@calcite.apache.org by "Julian Hyde (JIRA)" <ji...@apache.org> on 2015/03/31 03:20:54 UTC

[jira] [Updated] (CALCITE-656) Write tests for PreparedStatement.setXxx and ResultSet.getXxx

     [ https://issues.apache.org/jira/browse/CALCITE-656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Julian Hyde updated CALCITE-656:
--------------------------------
    Labels: avatica  (was: )

> Write tests for PreparedStatement.setXxx and ResultSet.getXxx
> -------------------------------------------------------------
>
>                 Key: CALCITE-656
>                 URL: https://issues.apache.org/jira/browse/CALCITE-656
>             Project: Calcite
>          Issue Type: Bug
>            Reporter: Julian Hyde
>            Assignee: Julian Hyde
>              Labels: avatica
>
> Write exhaustive tests for all of the PreparedStatement.setXxx methods, PreparedStatement.setObject(int, Object) (i.e. converting to what Calcite thinks the parameter should be), and all of the ResultSet.getXxx methods, testing every allowed combination of source and destination types.
> In CalciteRemoteDriverTest.testParameterConvert, I test PreparedStatement.setObject(int, Object, int) with every combination of source & destination types that are allowed by the JDBC spec. (SqlType.canGet and .canSet contains the type mappings from the spec.). So the new tests could be built in a similar way.



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