Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <1013919216.1143573682285.JavaMail.jira@ajax>
Date: Tue, 28 Mar 2006 20:21:22 +0100 (BST)
From: "Daniel John Debrunner (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Created: (DERBY-1159) PreparedStatement.executeUpdate throws
 a XJ05C exception in a global transaction if the statement is
 HOLD_CURSORS_OVER_COMMIT
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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.1.2.1, 10.2.0.0    
    Reporter: Daniel John Debrunner
 Assigned to: Daniel John Debrunner 
    Priority: Minor


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