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/02/05 07:06:00 UTC
[jira] [Commented] (IGNITE-21539) Improve test coverage for JDBC transactions
[ https://issues.apache.org/jira/browse/IGNITE-21539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17923934#comment-17923934 ]
Pavel Pereslegin commented on IGNITE-21539:
-------------------------------------------
[~jooger], please take a look at the proposed patch.
> Improve test coverage for JDBC transactions
> -------------------------------------------
>
> Key: IGNITE-21539
> URL: https://issues.apache.org/jira/browse/IGNITE-21539
> Project: Ignite
> Issue Type: Improvement
> Components: jdbc
> Reporter: Iurii Gerzhedovich
> Assignee: Pavel Pereslegin
> Priority: Major
> Labels: ignite-3
> Time Spent: 10m
> Remaining Estimate: 0h
>
> During implementation support of transaction for JDBCÂ were added set of tests. However added set of tests is insufficient.
> Let's add the following test scenarios:
> * Check that the transaction is rolled back after the connection/statement is closed.
> * Ensure that explicit transactions are rolled back if a client disconnects in the middle of the process.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)