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/09 11:51:18 UTC
[jira] [Comment Edited] (IGNITE-5339) JDBC thin driver: validate
compliance
[ https://issues.apache.org/jira/browse/IGNITE-5339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16044273#comment-16044273 ]
Taras Ledkov edited comment on IGNITE-5339 at 6/9/17 11:50 AM:
---------------------------------------------------------------
[Test results|http://195.239.208.174/project.html?projectId=Ignite20Tests&tab=projectOverview&branch_Ignite20Tests=pull%2F2112%2Fhead] are OK with me.
[~vozerov], please review the patch.
was (Author: tledkov-gridgain):
Waits for [test results|http://195.239.208.174/project.html?projectId=Ignite20Tests&tab=projectOverview&branch_Ignite20Tests=pull%2F2112%2Fhead]
> JDBC thin 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
> Labels: important
> 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)