[
https://issues.apache.org/jira/browse/IGNITE-18985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yury Gerzhedovich updated IGNITE-18985:
---------------------------------------
Description:
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..
was:
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.
> 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)
