db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (DERBY-2064) Network client setTransactionIsolation() commits any active transactions
Date Thu, 25 Aug 2011 22:08:30 GMT

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

Myrna van Lunteren resolved DERBY-2064.
---------------------------------------

       Resolution: Duplicate
    Fix Version/s: 10.7.1.1

I think this can then be closed as a duplicate. 

> 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
>              Labels: derby_triage10_5_2
>             Fix For: 10.7.1.1
>
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message