[
https://issues.apache.org/jira/browse/IGNITE-26141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin updated IGNITE-26141:
--------------------------------------
Summary: Sql. Jdbc. Migrate (Prepared)Statement to use thin client SQL API
(single statements) (was: Sql. Jdbc. Migrate (Prepared)Statement to use thin
client SQL API)
> Sql. Jdbc. Migrate (Prepared)Statement to use thin client SQL API (single
> statements)
> -------------------------------------------------------------------------------------
>
> Key: IGNITE-26141
> URL: https://issues.apache.org/jira/browse/IGNITE-26141
> Project: Ignite
> Issue Type: Improvement
> Components: jdbc ai3, sql ai3
> Reporter: Pavel Pereslegin
> Priority: Major
> Labels: ignite-3
>
> We need to (re-)implement (Prepared)Statement.executeQuery() to use
> ClientSql.execute().
> We can't change existing {{JdbcResultSet}} yet, so as part of this task we
> need to add a second {{java.sql.ResultSet}} implementation which will be the
> adapter for org.apache.ignite.sql.ResultSet.
> Migration of (Prepared)Statement.execute() (multistatement=true)) is out of
> scope of this task.
> It will 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)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
