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 "Deepa Remesh (JIRA)" <de...@db.apache.org> on 2005/10/21 21:49:20 UTC
[jira] Created: (DERBY-639) Statements in stored procedures with holdable cursor should not be allowed to execute in xa global transaction
Statements in stored procedures with holdable cursor should not be allowed to execute in xa global transaction
--------------------------------------------------------------------------------------------------------------
Key: DERBY-639
URL: http://issues.apache.org/jira/browse/DERBY-639
Project: Derby
Type: Bug
Components: JDBC
Versions: 10.2.0.0
Reporter: Deepa Remesh
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.
-
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
[jira] Updated: (DERBY-639) Statements in stored procedures with
holdable cursor should not be allowed to execute in xa global transaction
Posted by "Mike Matrigali (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (DERBY-639) Statements in stored procedures with holdable cursor should not be allowed to execute in xa global transaction
Posted by "Deepa Remesh (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-639?page=all ]
Deepa Remesh updated DERBY-639:
-------------------------------
Attachment: d639.sql
d639.java
Attaching a repro for this. To see the problem, run d639.sql using ij. The stored procedure used in the sql is in d639.java.
Currently, the sql runs successfully and the behaviour is same in local and global transaction. This does not seem right. It should give an error when executing this procedure in a global transaction.
> Statements in stored procedures with holdable cursor should not be allowed to execute in xa global transaction
> --------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-639
> URL: http://issues.apache.org/jira/browse/DERBY-639
> Project: Derby
> Type: Bug
> Components: JDBC
> Versions: 10.2.0.0
> 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.
-
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