You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Yury Gerzhedovich (Jira)" <ji...@apache.org> on 2023/03/09 15:13:00 UTC

[jira] [Updated] (IGNITE-18985) Sql. Jdbc. Integration with transaction

     [ https://issues.apache.org/jira/browse/IGNITE-18985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yury Gerzhedovich updated IGNITE-18985:
---------------------------------------
    Epic Link: IGNITE-14858

> Sql. Jdbc. Integration with transaction
> ---------------------------------------
>
>                 Key: IGNITE-18985
>                 URL: https://issues.apache.org/jira/browse/IGNITE-18985
>             Project: Ignite
>          Issue Type: Improvement
>          Components: jdbc
>            Reporter: Konstantin Orlov
>            Priority: Major
>              Labels: ignite-3
>
> Current implementation of JDBC misses integration with transactions. 
> So, new command should be introduced to client-server protocol: {{{}finishTx(commit: bool){}}}. According handler should be provided on a server side. This command may be issued by invocation of commit/rollback methods on {{{}JdbcConnection{}}}.
> Also, we need to handle {{setAutoCommit}} method invocation as well.
> Finally, depending on current mode of autoCommit and presence of valid transaction in connection context, the new transaction should or should not be issued before query execution. It looks like we can rely on implicit transactions right now, thus if autoCommit set to true, it seems to safe to provide null instead of actual transaction. However, autoCommit=false mode must be handled explicitly.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)