You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Taras Ledkov (JIRA)" <ji...@apache.org> on 2017/06/08 12:59:18 UTC

[jira] [Assigned] (IGNITE-5339) Thin JDBC driver: validate compliance

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

Taras Ledkov reassigned IGNITE-5339:
------------------------------------

    Assignee: Taras Ledkov  (was: Sergey Kalashnikov)

> Thin JDBC driver: validate compliance
> -------------------------------------
>
>                 Key: IGNITE-5339
>                 URL: https://issues.apache.org/jira/browse/IGNITE-5339
>             Project: Ignite
>          Issue Type: Task
>          Components: sql
>            Reporter: Vladimir Ozerov
>            Assignee: Taras Ledkov
>             Fix For: 2.1
>
>
> We need to make sure that all methods of our new driver are compliant with JDBC spec, namely:
> 1) Semantics of normal execution is correct
> 2) Exceptions are thrown when excepted
> I propose the following flow:
> 1) Walk through interface classes (Connection -> Statement, PreparedStatement -> ResultSet)
> 2) For every method identify a set of tests to verify semantics (if any).
> 3) Write those tests, even if they fail.
> 4) Once all tests are ready, decide how to proceed with their fixes.
> NB: we should write tests even for methods which throw "not-implemented exception", so that we better understand the scope of remaining work.
> Link to [JDBC specification|http://download.oracle.com/otn-pub/jcp/jdbc-4_1-mrel-spec/jdbc4.1-fr-spec.pdf?AuthParam=1496141650_c2ec45f13eb8c532632bbfaede64f351]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)