[
https://issues.apache.org/jira/browse/DERBY-3427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569891#action_12569891
]
Knut Anders Hatlen commented on DERBY-3427:
-------------------------------------------
The following commit introduced the problem:
------------------------------------------------------------------------
r542011 | kahatlen | 2007-05-27 19:56:32 +0200 (Sun, 27 May 2007) | 16 lines
DERBY-2496: Implement Blob support for Locators
The attached patch, enableblobloc.diff, contains the the necessary
changes to enable the use of locators for Blob. The patch addresses
the following issues:
* Enable the use of locators.
* Modification of tests that experience changed behavior with locators
* If stored procedures reports that the given locator can not be
found, it is assumed that this is because transaction has been
terminated and an "Blob accessed after commit" error is
reported. This makes the client driver and the embedded driver
report the same error for this case.
Contributed by Øystein Grøvlen.
------------------------------------------------------------------------
> 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.
