[
https://issues.apache.org/jira/browse/IGNITE-4922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15984557#comment-15984557
]
Taras Ledkov edited comment on IGNITE-4922 at 4/26/17 1:12 PM:
---------------------------------------------------------------
The features supported by Ignite client-based JdbcConnection (v2) to support in
the thin JdbcConnection:
* JdbcStatement
** executeUpdate;
** getUpdateCount;
** addBatch / clearBatch;
Major unsupported features:
* transactions;
* procedures;
* scrollable cursor and writable cursor;
* mapping SQL Data Types into Java;
* streams as query parameters;
* batches;
* multiple result set;
Minor unsupported features:
* statement cancellation (the one thread cancels the statement that is executed
by another thread);
* named cursor;
* pollable statements;
* closeOnCompletion statement (a statement will be closed when all its
dependent result sets are closed)
* prepared statement metadata;
* catalogs;
* query timeout;
* access to auto-generated fields (auto-generated fields haven't supported by
Ignite DDL yet).
was (Author: tledkov-gridgain):
The features supported by Ignite client-based JdbcConnection (v2) to support in
the thin JdbcConnection:
* JdbcStatement
** executeUpdate;
** getUpdateCount;
** addBatch / clearBatch;
Unsupported features:
* transactions;
* procedures;
* scrollable cursor and writable cursor;
* mapping SQL Data Types into Java;
* streams as query parameters;
* batches;
* multiple result set;
> JDBC Driver: renew thin client based solution
> ---------------------------------------------
>
> Key: IGNITE-4922
> URL: https://issues.apache.org/jira/browse/IGNITE-4922
> Project: Ignite
> Issue Type: Task
> Reporter: Denis Magda
> Fix For: 2.1
>
>
> This is a parent ticket for all the activities that are intended to improve
> the thin client based implementation of the JDBC driver making it default one.
>
> Refer to the corresponding discussion on the dev list:
> http://apache-ignite-developers.2346864.n4.nabble.com/jdbc-vs-jdbc2-packages-td14309.html
> In a nutshell, depending on a type of a protocol to be used for the next-gen
> version the options are the following:
> - This type of driver might be a default driver for tools and applications
> that don't need transactional support. Existing REST based protocol can be
> used for this scenario.
> - If we want to support transactions (which is optional at the beginning)
> then Yakov solution (see discussion) can be applied. However, it makes sense
> to implement it only after MVCC is ready.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
