db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dyre Tjeldvoll (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-3496) CallableStatement with output parameter leaves cursor open after execution
Date Tue, 25 Mar 2008 12:41:25 GMT

     [ 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.


Mime
View raw message