db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-2064) Network client setTransactionIsolation() commits any active transactions
Date Wed, 08 Jul 2009 08:54:14 GMT

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

Knut Anders Hatlen updated DERBY-2064:
--------------------------------------

      Issue & fix info: [Release Note Needed, Repro attached]
               Urgency: Normal
    Bug behavior facts: [Embedded/Client difference]
               Summary: Network client setTransactionIsolation() commits any active transactions
 (was: Network client setTransactionIsolation() commits any active transactios)

Triaged for 10.5.2. A test case for this is included in jdbcapi/SetTransactionIsolationTest
(testSetTransactionIsolationCommits), so setting "Repro attached".

> Network client setTransactionIsolation() commits any active transactions
> ------------------------------------------------------------------------
>
>                 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.


Mime
View raw message