[
https://issues.apache.org/jira/browse/DERBY-3427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12575640#action_12575640
]
Knut Anders Hatlen commented on DERBY-3427:
-------------------------------------------
> which in turn should reduce resource consumption
The committed patch does however make all callable statements have a cursor
name (before the patch, only prepared statements and statements had cursor
names), which could increase the resource consumption. Is there any scenario
where a CALL statement can make use of the cursor name, or should I create a
follow-up patch which reverts to the old behaviour and skips setting the cursor
name for CALLs?
> 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.
