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

Pavel Pereslegin updated IGNITE-26140:
--------------------------------------
    Description: 
This is a preparation step for migrating current JDBC driver implementation to 
use thin client SQL API. The current implementation (JdbcResultSet) should not 
change.

We need to add a new implementation for java.sql.ResultSet that will use 
org.apache.ignite.sql.ResultSet for source of data.
To do this we will also need to add a second implementation of 
ResultSetMetaData.

It will be necessary to add separate unit tests for the expected behavior of 
the adapter.

  was:
We need to (re-)implement {{PreparedStatement.executeBatch()}} to use 
{{ClientSql.executeBatch()}}.

It will also be necessary to support the following:

1. Cancellation token (see how it is done in IGNITE-26139)
2. Pass client time zone (see 
JdbcConnection.connectionProperties().getConnectionTimeZone) as statement 
properties.
3. Pass transaction in non-autocommit mode (see how it is done in IGNITE-26139)


> Sql. Jdbc. Add new implementation for java.sql.ResultSet (adapter for 
> org.apache.ignite.sql.ResultSet).
> -------------------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-26140
>                 URL: https://issues.apache.org/jira/browse/IGNITE-26140
>             Project: Ignite
>          Issue Type: Improvement
>          Components: jdbc ai3, sql ai3
>            Reporter: Pavel Pereslegin
>            Priority: Major
>              Labels: ignite-3
>
> This is a preparation step for migrating current JDBC driver implementation 
> to use thin client SQL API. The current implementation (JdbcResultSet) should 
> not change.
> We need to add a new implementation for java.sql.ResultSet that will use 
> org.apache.ignite.sql.ResultSet for source of data.
> To do this we will also need to add a second implementation of 
> ResultSetMetaData.
> It will be necessary to add separate unit tests for the expected behavior of 
> the adapter.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to