[ http://issues.apache.org/jira/browse/DERBY-1158?page=comments#action_12372171 ]
Daniel John Debrunner commented on DERBY-1158: ---------------------------------------------- JDBC 4.0 section 16.1.3.1 provides helpful information on addressing this: namely if a data source cannot support a holdability level then it can select another and add a warning (currently derby in a global transaction throws an error) the application must check the holdability of its ResultSet and not rely on it matching the statement's or connection setting. > Allow use of Statements created in local transaction with default holdability > to be used in global transactions. > ---------------------------------------------------------------------------------------------------------------- > > Key: DERBY-1158 > URL: http://issues.apache.org/jira/browse/DERBY-1158 > Project: Derby > Type: Improvement > Components: JDBC, Network Client > Versions: 10.1.2.1 > Reporter: Daniel John Debrunner > Assignee: Daniel John Debrunner > > A statement created or prepared in a local transaction using the default > holdability settting can not be used in a global transaction. > This is because the default holdability is HOLD_CURSORS_OVER_COMMIT and Derby > does not support held cursors in global transactions. > The change would be to allow those statements to be used in global > transactions, returning ResultSets that are CLOSE_CURSORS_AT_COMMIT . > This would allow such statements to be cached by application servers. > JDBC 3.0 section 12.6 does allow holdability to be handled in an > implementation specific way for global transactions. > I believe this change is forward compatible if Derby ever does start > supporting held cursors in global transactions (pretty unlikely) since > the functionality displayed is a ub-set of the holdable functionality. -- 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
