[
https://issues.apache.org/jira/browse/IGNITE-26139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin updated IGNITE-26139:
--------------------------------------
Description:
We need to (re-)implement Statement.executeUpdate using ClientSql (internal)
API .
After IGNITE-26086 internal API to execute query with specified query type
should be implemented.
executeUpdate() must use this API to execute query (query type = DML/DDL).
Most likely, it will also be necessary to support the following:
1. Cancellation token (to be able cancel query)
2. Pass client time zone (see
JdbcConnection.connectionProperties().getConnectionTimeZone) as statement
property.
3. Pass transaction if autocommit=false mode (similar to what we have on server
side - we need to lazily start transaction if it isn't started yet)
was:
We need to (re-)implement Statement.executeUpdate using ClientSql (internal)
API .
After IGNITE-26086 internal API to execute query with specified query type
should be implemented.
executeUpdate() must use this API to execute query (query type = DML/DDL).
Most likely, it will also be necessary to support the following:
1. Cancellation token (to be able cancel query)
2. Pass client time zone (see
JdbcConnection.connectionProperties().getConnectionTimeZone) as statement
properties.
3. Pass transaction if autocommit=false mode (similar to what we have on server
side - we need to lazily start transaction if it isn't started yet)
> Sql. Jdbc. Migrate Statement.executeUpdate() to use thin client SQL API
> -----------------------------------------------------------------------
>
> Key: IGNITE-26139
> URL: https://issues.apache.org/jira/browse/IGNITE-26139
> Project: Ignite
> Issue Type: New Feature
> Components: jdbc ai3, sql ai3
> Reporter: Pavel Pereslegin
> Priority: Major
>
> We need to (re-)implement Statement.executeUpdate using ClientSql (internal)
> API .
> After IGNITE-26086 internal API to execute query with specified query type
> should be implemented.
> executeUpdate() must use this API to execute query (query type = DML/DDL).
> Most likely, it will also be necessary to support the following:
> 1. Cancellation token (to be able cancel query)
> 2. Pass client time zone (see
> JdbcConnection.connectionProperties().getConnectionTimeZone) as statement
> property.
> 3. Pass transaction if autocommit=false mode (similar to what we have on
> server side - we need to lazily start transaction if it isn't started yet)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
