[DERBY-639] Statements in stored procedures with holdable cursor should not be allowed to execute in xa global transaction

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 10.2.1.6
• Component/s: JDBC
• Labels: derby_triage10_5_2
• Urgency: Normal
• Bug behavior facts: Deviation from standard
• Assignee: Unassigned
• Reporter: Deepa
• Created: 22/Oct/05 04:48
• Updated: 15/Feb/11 21:08

Description

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"); }

Issue Links

• is part of: DERBY-1158 Allow use of Statements created in local transaction with default holdability to be used in global transactions.