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] Commented: (DERBY-3427) setting transaction isolation level to read committed raise ERROR X0X03: Invalid transaction state - held cursor requires same isolation level
Date Thu, 13 Mar 2008 08:39:47 GMT

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

Knut Anders Hatlen commented on DERBY-3427:
-------------------------------------------

I guess that if we find out that the cursor name does make any difference, it's a better solution
to make sure the network server doesn't set a cursor name unless the client has done so, rather
than reintroducing the asymmetry between CallableStatement and PreparedStatement. (Of course,
the best solution is to fix the overhead of named cursors in the embedded driver, if such
an overhead exists.)

As to the question about setting 'existing application impact' flag, I'm leaning towards not
setting it. Holdable cursors is the default, so the users must have made a deliberate choice
that they want non-holdable cursors, and then they shouldn't expect the cursors to be holdable.

> 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.3.2.2, 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