db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dyre Tjeldvoll (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3427) setting transaction isolation level to read committed raise ERROR X0X03: Invalid transaction state - held cursor requires same isolation level
Date Thu, 06 Mar 2008 13:56:59 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12575710#action_12575710
] 

Dyre Tjeldvoll commented on DERBY-3427:
---------------------------------------

Knut> should I create a follow-up patch which reverts to the old behaviour and skips setting
the cursor name for CALLs?

Your CALL (pun intended). I have a hard time seeing that it would make a huge difference,
but without testing it you never know, I guess...

Should we set 'Existing application impact' on this issue? Theoretically, someone could have
come to expect that cursors are always holdable for CallableStatement when using the ClientDriver.

> setting transaction isolation level to read committed raise ERROR X0X03: Invalid transaction
state - held cursor requires same isolation level
> ----------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3427
>                 URL: https://issues.apache.org/jira/browse/DERBY-3427
>             Project: Derby
>          Issue Type: Bug
>    Affects Versions: 10.3.1.4, 10.3.2.1
>         Environment: windows XP Java version 1.6.0_03
>            Reporter: Rene Levantinh
>            Assignee: Knut Anders Hatlen
>            Priority: Critical
>             Fix For: 10.4.0.0
>
>         Attachments: d3427.diff, SimpleNetworkClientSample1.java, SimpleNetworkServerSample.java,
use-holdability.diff
>
>
> setting transaction isolation level to read committed after reading a BLOG record raise
ERROR X0X03: Invalid transaction state - held cursor requires same isolation level .
>   Using Derby client 10.2  either with Derby  server 10.3  or  10.2   works fine .
>   Using Derby Client 10.3  with Derby Server 10.2  also work fine.  

-- 
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