[
https://issues.apache.org/jira/browse/DERBY-2064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478298
]
Knut Anders Hatlen commented on DERBY-2064:
-------------------------------------------
> This differs from the embedded driver, where setTransactionIsolation() does
> not cause a commit.
More precisely: ... where setTransactionIsolation() only commits if the
isolation level is changed.
> Network client setTransactionIsolation() commits any active transactios
> -----------------------------------------------------------------------
>
> Key: DERBY-2064
> URL: https://issues.apache.org/jira/browse/DERBY-2064
> Project: Derby
> Issue Type: Bug
> Components: Network Client
> Reporter: Bernt M. Johnsen
>
> Network client implements setTransactionIsolation() using
> Statement.executeUpdate("SET CURRENT ISOLATION.......")
> which again causes any active transactions to commit.
> This differs from the embedded driver, where setTransactionIsolation() does
> not cause a commit.
> (Note that "SET CURRENT ISOLATION....." will commit active transactions
> idependent of this)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
