Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <2039812995.1203333514822.JavaMail.jira@brutus>
Date: Mon, 18 Feb 2008 03:18:34 -0800 (PST)
From: "Dyre Tjeldvoll (JIRA)" <jira@apache.org>
To: derby-dev@db.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
In-Reply-To: <752077163.1203272794735.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

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

I assume that you mean BLOB (not BLOG)? 
Are you saying that this is a regression from 10.2 to 10.3?

Your example contains quite a bit of code. Can you pinpoint where you're getting the error?
Did you try the same query with other data types (not BLOB/CLOB)?


> 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
>            Priority: Critical
>         Attachments: SimpleNetworkClientSample1.java, SimpleNetworkServerSample.java
>
>
> 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.