[
https://issues.apache.org/jira/browse/DERBY-639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Matrigali updated DERBY-639:
---------------------------------
Urgency: Normal
Bug behavior facts: [Deviation from standard]
Triaged July 2, 2009: Marked as non standard and assigned normal urgency.
> Statements in stored procedures with holdable cursor should not be allowed to
> execute in xa global transaction
> --------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-639
> URL: https://issues.apache.org/jira/browse/DERBY-639
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.2.1.6
> Reporter: Deepa Remesh
> Attachments: d639.java, d639.sql
>
>
> Execution of statements with HOLD_CURSORS_OVER_COMMIT must not be allowed in
> a global transaction. Currently, this is allowed when the statement is inside
> a stored procedure.
> e.g: The following procedure should throw an error when executed inside a
> global transaction. However, no error is thrown when running with embedded or
> client drivers.
> //Java method for stored procedure with HOLD_CURSORS_OVER_COMMIT
> public static void testHoldCursorsProc(ResultSet[] rs) throws Exception
> {
> Connection conn =
> DriverManager.getConnection("jdbc:default:connection");
> //HOLD_CURSORS_OVER_COMMIT
> Statement st =
> conn.createStatement(ResultSet.TYPE_SCROLL_INSENSITIVE ,
> ResultSet.CONCUR_READ_ONLY,
> ResultSet.HOLD_CURSORS_OVER_COMMIT);
> rs[0] = st.executeQuery("select * from testtable1");
> }
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
