[
https://issues.apache.org/jira/browse/IGNITE-23965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin updated IGNITE-23965:
--------------------------------------
Fix Version/s: 3.0
> Sql. Jdbc update counter for DDL/KILL statements must always be zero.
> ---------------------------------------------------------------------
>
> Key: IGNITE-23965
> URL: https://issues.apache.org/jira/browse/IGNITE-23965
> Project: Ignite
> Issue Type: Improvement
> Components: sql
> Reporter: Pavel Pereslegin
> Assignee: Pavel Pereslegin
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In IGNITE-23440, along with the introduction of the new KILL command, it was
> decided to improve the current behavior of DDL statements and add the ability
> to understand using JDBC whether the command was applied or not.
> However, this change may be confusing to users because the JDBC javadoc
> states that the DDL command returns nothing (which is not true for AI3, where
> the DDL command returns a boolean).
> Anyway, we decided to return to the old behavior in JDBC, where the update
> counter always remains zero when executing a DDL command (the same applies to
> the KILL command).
> It is necessary to roll back the related changes made in IGNITE-23440.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
