You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Bernt M. Johnsen (JIRA)" <ji...@apache.org> on 2006/11/09 09:53:37 UTC

[jira] Created: (DERBY-2064) Network client setTransactionIsolation() commits any active transactios

Network client setTransactionIsolation() commits any active transactios
-----------------------------------------------------------------------

                 Key: DERBY-2064
                 URL: http://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.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Updated: (DERBY-2064) Network client setTransactionIsolation() commits any active transactions

Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
     [ 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.


[jira] Commented: (DERBY-2064) Network client setTransactionIsolation() commits any active transactios

Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
    [ 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.