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 "Andrew McIntyre (JIRA)" <de...@db.apache.org> on 2006/04/24 23:00:06 UTC
[jira] Reopened: (DERBY-1159) PreparedStatement.executeUpdate
throws a XJ05C exception in a global transaction if the statement is
HOLD_CURSORS_OVER_COMMIT
[ http://issues.apache.org/jira/browse/DERBY-1159?page=all ]
Andrew McIntyre reopened DERBY-1159:
------------------------------------
> PreparedStatement.executeUpdate throws a XJ05C exception in a global transaction if the statement is HOLD_CURSORS_OVER_COMMIT
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-1159
> URL: http://issues.apache.org/jira/browse/DERBY-1159
> Project: Derby
> Type: Bug
> Versions: 10.2.0.0, 10.1.2.1
> Reporter: Daniel John Debrunner
> Assignee: Daniel John Debrunner
> Priority: Minor
> Fix For: 10.2.0.0, 10.1.3.0, 10.1.2.4
>
> SQLSTATE(XJ05C): Cannot set holdability ResultSet.HOLD_CURSORS_OVER_COMMIT for
> a global transaction.
> Exception is thrown in client, in embedded the statement executes successfully.
> Since HOLD_CURSORS_OVER_COMMIT only applies to ResultSets and executeUpdate states it only succeeds if the statement
> does not generate ResultSets, then this combination should succeed.
> Probably related to the fact that in embedded an execute() call on the same PreparedStatement will thrown a XJ05C exception
> Workaround is to prepare the statement explicitly with CLOSE_CURSORS_AT_COMMIT.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira