You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Knut Anders Hatlen (JIRA)" <ji...@apache.org> on 2008/03/05 13:17:41 UTC
[jira] Created: (DERBY-3496) CallableStatement with output
parameter leaves cursor open after execution
CallableStatement with output parameter leaves cursor open after execution
--------------------------------------------------------------------------
Key: DERBY-3496
URL: https://issues.apache.org/jira/browse/DERBY-3496
Project: Derby
Issue Type: Bug
Components: JDBC
Affects Versions: 10.4.0.0
Reporter: Knut Anders Hatlen
Priority: Minor
When executing a CallableStatement which has an output parameter, the language result set is left open and makes subsequent calls to Connection.setTransactionIsolation() fail with "ERROR X0X03: Invalid transaction state - held cursor requires same isolation level".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (DERBY-3496) CallableStatement with output
parameter leaves cursor open after execution
Posted by "Dyre Tjeldvoll (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dyre Tjeldvoll reassigned DERBY-3496:
-------------------------------------
Assignee: Dyre Tjeldvoll
> CallableStatement with output parameter leaves cursor open after execution
> --------------------------------------------------------------------------
>
> Key: DERBY-3496
> URL: https://issues.apache.org/jira/browse/DERBY-3496
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.4.0.0
> Reporter: Knut Anders Hatlen
> Assignee: Dyre Tjeldvoll
> Priority: Minor
> Fix For: 10.3.2.2, 10.4.0.0
>
> Attachments: junit-repro.diff
>
>
> When executing a CallableStatement which has an output parameter, the language result set is left open and makes subsequent calls to Connection.setTransactionIsolation() fail with "ERROR X0X03: Invalid transaction state - held cursor requires same isolation level".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-3496) CallableStatement with output
parameter leaves cursor open after execution
Posted by "Dyre Tjeldvoll (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dyre Tjeldvoll updated DERBY-3496:
----------------------------------
Attachment: derby-3496.diff
Attaching derby-3496.diff which incorporates the new test case attached earlier.
> CallableStatement with output parameter leaves cursor open after execution
> --------------------------------------------------------------------------
>
> Key: DERBY-3496
> URL: https://issues.apache.org/jira/browse/DERBY-3496
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.4.0.0
> Reporter: Knut Anders Hatlen
> Assignee: Dyre Tjeldvoll
> Priority: Minor
> Fix For: 10.3.2.2, 10.4.0.0
>
> Attachments: derby-3496.diff, junit-repro.diff
>
>
> When executing a CallableStatement which has an output parameter, the language result set is left open and makes subsequent calls to Connection.setTransactionIsolation() fail with "ERROR X0X03: Invalid transaction state - held cursor requires same isolation level".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-3496) CallableStatement with output
parameter leaves cursor open after execution
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12581023#action_12581023 ]
Knut Anders Hatlen commented on DERBY-3496:
-------------------------------------------
The fix looks correct to me, but the new line in EmbedCallableStatement is not indented correctly (probably due to incorrect tab size setting in your IDE).
> CallableStatement with output parameter leaves cursor open after execution
> --------------------------------------------------------------------------
>
> Key: DERBY-3496
> URL: https://issues.apache.org/jira/browse/DERBY-3496
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.4.0.0
> Reporter: Knut Anders Hatlen
> Assignee: Dyre Tjeldvoll
> Priority: Minor
> Fix For: 10.3.2.2, 10.4.0.0
>
> Attachments: derby-3496.diff, junit-repro.diff
>
>
> When executing a CallableStatement which has an output parameter, the language result set is left open and makes subsequent calls to Connection.setTransactionIsolation() fail with "ERROR X0X03: Invalid transaction state - held cursor requires same isolation level".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-3496) CallableStatement with output
parameter leaves cursor open after execution
Posted by "Dyre Tjeldvoll (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12581934#action_12581934 ]
Dyre Tjeldvoll commented on DERBY-3496:
---------------------------------------
Merged to 10.4 in revision 640801.
> CallableStatement with output parameter leaves cursor open after execution
> --------------------------------------------------------------------------
>
> Key: DERBY-3496
> URL: https://issues.apache.org/jira/browse/DERBY-3496
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.4.0.0
> Reporter: Knut Anders Hatlen
> Assignee: Dyre Tjeldvoll
> Priority: Minor
> Fix For: 10.3.2.2, 10.4.0.0
>
> Attachments: derby-3496.diff, junit-repro.diff
>
>
> When executing a CallableStatement which has an output parameter, the language result set is left open and makes subsequent calls to Connection.setTransactionIsolation() fail with "ERROR X0X03: Invalid transaction state - held cursor requires same isolation level".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-3496) CallableStatement with output
parameter leaves cursor open after execution
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12575323#action_12575323 ]
Knut Anders Hatlen commented on DERBY-3496:
-------------------------------------------
If the CallableStatement is closed before the isolation level is changed, it works in embedded mode, but it still fails the same way in client/server mode.
> CallableStatement with output parameter leaves cursor open after execution
> --------------------------------------------------------------------------
>
> Key: DERBY-3496
> URL: https://issues.apache.org/jira/browse/DERBY-3496
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.4.0.0
> Reporter: Knut Anders Hatlen
> Priority: Minor
> Attachments: junit-repro.diff
>
>
> When executing a CallableStatement which has an output parameter, the language result set is left open and makes subsequent calls to Connection.setTransactionIsolation() fail with "ERROR X0X03: Invalid transaction state - held cursor requires same isolation level".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-3496) CallableStatement with output
parameter leaves cursor open after execution
Posted by "Dyre Tjeldvoll (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dyre Tjeldvoll updated DERBY-3496:
----------------------------------
Fix Version/s: 10.4.0.0
10.3.2.2
Adding 10.3.2.2 and 10.4.0.0 as fix versions as it looks like a candidate for merging to 10.3
> CallableStatement with output parameter leaves cursor open after execution
> --------------------------------------------------------------------------
>
> Key: DERBY-3496
> URL: https://issues.apache.org/jira/browse/DERBY-3496
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.4.0.0
> Reporter: Knut Anders Hatlen
> Priority: Minor
> Fix For: 10.3.2.2, 10.4.0.0
>
> Attachments: junit-repro.diff
>
>
> When executing a CallableStatement which has an output parameter, the language result set is left open and makes subsequent calls to Connection.setTransactionIsolation() fail with "ERROR X0X03: Invalid transaction state - held cursor requires same isolation level".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-3496) CallableStatement with output
parameter leaves cursor open after execution
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Knut Anders Hatlen updated DERBY-3496:
--------------------------------------
Attachment: junit-repro.diff
The attached patch (junit-repro.diff) adds a test case to jdbcapi/CallableTest which fails in both embedded and client/server mode.
$ java junit.textui.TestRunner org.apache.derbyTesting.functionTests.tests.jdbcapi.CallableTest
....E.............E.........
Time: 6.071
There were 2 errors:
1) testIsolationLevelChangeAfterFunctionCall(org.apache.derbyTesting.functionTests.tests.jdbcapi.CallableTest)java.sql.SQLException: Invalid transaction state - held cursor requires same isolation level
....
2) testIsolationLevelChangeAfterFunctionCall(org.apache.derbyTesting.functionTests.tests.jdbcapi.CallableTest)java.sql.SQLException: Invalid transaction state - held cursor requires same isolation level
....
> CallableStatement with output parameter leaves cursor open after execution
> --------------------------------------------------------------------------
>
> Key: DERBY-3496
> URL: https://issues.apache.org/jira/browse/DERBY-3496
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.4.0.0
> Reporter: Knut Anders Hatlen
> Priority: Minor
> Attachments: junit-repro.diff
>
>
> When executing a CallableStatement which has an output parameter, the language result set is left open and makes subsequent calls to Connection.setTransactionIsolation() fail with "ERROR X0X03: Invalid transaction state - held cursor requires same isolation level".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-3496) CallableStatement with output
parameter leaves cursor open after execution
Posted by "Dyre Tjeldvoll (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dyre Tjeldvoll updated DERBY-3496:
----------------------------------
Derby Info: (was: [Patch Available])
Committed revision 640787.
I did fix the indentation problem before committing. The "IDE" in question is 'vi'. :set hardtabs=4 (perhaps followed by :set autoindent) appears to be the magic words.
> CallableStatement with output parameter leaves cursor open after execution
> --------------------------------------------------------------------------
>
> Key: DERBY-3496
> URL: https://issues.apache.org/jira/browse/DERBY-3496
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.4.0.0
> Reporter: Knut Anders Hatlen
> Assignee: Dyre Tjeldvoll
> Priority: Minor
> Fix For: 10.3.2.2, 10.4.0.0
>
> Attachments: derby-3496.diff, junit-repro.diff
>
>
> When executing a CallableStatement which has an output parameter, the language result set is left open and makes subsequent calls to Connection.setTransactionIsolation() fail with "ERROR X0X03: Invalid transaction state - held cursor requires same isolation level".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-3496) CallableStatement with output
parameter leaves cursor open after execution
Posted by "Dyre Tjeldvoll (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dyre Tjeldvoll updated DERBY-3496:
----------------------------------
Derby Info: [Patch Available]
> CallableStatement with output parameter leaves cursor open after execution
> --------------------------------------------------------------------------
>
> Key: DERBY-3496
> URL: https://issues.apache.org/jira/browse/DERBY-3496
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.4.0.0
> Reporter: Knut Anders Hatlen
> Assignee: Dyre Tjeldvoll
> Priority: Minor
> Fix For: 10.3.2.2, 10.4.0.0
>
> Attachments: derby-3496.diff, junit-repro.diff
>
>
> When executing a CallableStatement which has an output parameter, the language result set is left open and makes subsequent calls to Connection.setTransactionIsolation() fail with "ERROR X0X03: Invalid transaction state - held cursor requires same isolation level".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (DERBY-3496) CallableStatement with output
parameter leaves cursor open after execution
Posted by "Dyre Tjeldvoll (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dyre Tjeldvoll resolved DERBY-3496.
-----------------------------------
Resolution: Fixed
> CallableStatement with output parameter leaves cursor open after execution
> --------------------------------------------------------------------------
>
> Key: DERBY-3496
> URL: https://issues.apache.org/jira/browse/DERBY-3496
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.4.0.0
> Reporter: Knut Anders Hatlen
> Assignee: Dyre Tjeldvoll
> Priority: Minor
> Fix For: 10.3.2.2, 10.4.0.0
>
> Attachments: derby-3496.diff, junit-repro.diff
>
>
> When executing a CallableStatement which has an output parameter, the language result set is left open and makes subsequent calls to Connection.setTransactionIsolation() fail with "ERROR X0X03: Invalid transaction state - held cursor requires same isolation level".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-3496) CallableStatement with output
parameter leaves cursor open after execution
Posted by "Dyre Tjeldvoll (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12581940#action_12581940 ]
Dyre Tjeldvoll commented on DERBY-3496:
---------------------------------------
Merged to 10.3 with revision 640808.
> CallableStatement with output parameter leaves cursor open after execution
> --------------------------------------------------------------------------
>
> Key: DERBY-3496
> URL: https://issues.apache.org/jira/browse/DERBY-3496
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.4.0.0
> Reporter: Knut Anders Hatlen
> Assignee: Dyre Tjeldvoll
> Priority: Minor
> Fix For: 10.3.2.2, 10.4.0.0
>
> Attachments: derby-3496.diff, junit-repro.diff
>
>
> When executing a CallableStatement which has an output parameter, the language result set is left open and makes subsequent calls to Connection.setTransactionIsolation() fail with "ERROR X0X03: Invalid transaction state - held cursor requires same isolation level".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Reopened: (DERBY-3496) CallableStatement with output
parameter leaves cursor open after execution
Posted by "Dyre Tjeldvoll (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dyre Tjeldvoll reopened DERBY-3496:
-----------------------------------
Need to merge it to release branch
> CallableStatement with output parameter leaves cursor open after execution
> --------------------------------------------------------------------------
>
> Key: DERBY-3496
> URL: https://issues.apache.org/jira/browse/DERBY-3496
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.4.0.0
> Reporter: Knut Anders Hatlen
> Assignee: Dyre Tjeldvoll
> Priority: Minor
> Fix For: 10.3.2.2, 10.4.0.0
>
> Attachments: derby-3496.diff, junit-repro.diff
>
>
> When executing a CallableStatement which has an output parameter, the language result set is left open and makes subsequent calls to Connection.setTransactionIsolation() fail with "ERROR X0X03: Invalid transaction state - held cursor requires same isolation level".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (DERBY-3496) CallableStatement with output
parameter leaves cursor open after execution
Posted by "Dyre Tjeldvoll (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dyre Tjeldvoll resolved DERBY-3496.
-----------------------------------
Resolution: Fixed
> CallableStatement with output parameter leaves cursor open after execution
> --------------------------------------------------------------------------
>
> Key: DERBY-3496
> URL: https://issues.apache.org/jira/browse/DERBY-3496
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.4.0.0
> Reporter: Knut Anders Hatlen
> Assignee: Dyre Tjeldvoll
> Priority: Minor
> Fix For: 10.3.2.2, 10.4.0.0
>
> Attachments: derby-3496.diff, junit-repro.diff
>
>
> When executing a CallableStatement which has an output parameter, the language result set is left open and makes subsequent calls to Connection.setTransactionIsolation() fail with "ERROR X0X03: Invalid transaction state - held cursor requires same isolation level".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.