You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Pavel Pereslegin (Jira)" <ji...@apache.org> on 2025/08/06 14:04:00 UTC
[jira] [Created] (IGNITE-26141) Sql. Jdbc. Migrate (Prepared)Statement.executeQuery() to use thin client SQL API
Pavel Pereslegin created IGNITE-26141:
-----------------------------------------
Summary: Sql. Jdbc. Migrate (Prepared)Statement.executeQuery() to use thin client SQL API
Key: IGNITE-26141
URL: https://issues.apache.org/jira/browse/IGNITE-26141
Project: Ignite
Issue Type: New Feature
Components: jdbc ai3, sql ai3
Reporter: Pavel Pereslegin
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)