[ http://issues.apache.org/jira/browse/DERBY-1101?page=comments#action_12373440 ]
Daniel John Debrunner commented on DERBY-1101: ---------------------------------------------- Just to add that section 16.1.3.1 of JDBC 4.0 (proposed final draft) states: "In the case of a SQL CALL statement, the holdability of any returned ResultSets are determined by the stored procedure, independent of the holdability level specified to the SQL CALL statement." > ResultSet.getHoldabilty will return incorrect value when the ResultSet is > obtained from a procedure call > -------------------------------------------------------------------------------------------------------- > > Key: DERBY-1101 > URL: http://issues.apache.org/jira/browse/DERBY-1101 > Project: Derby > Type: Bug > Components: JDBC > Versions: 10.2.0.0 > Reporter: Daniel John Debrunner > Assignee: Knut Anders Hatlen > Priority: Minor > Attachments: derby-1101-testcase-v1.diff, derby-1101-v1.diff, > derby-1101-v1.stat, testderby1101.java > > EmbedResultSet40.getHoldability returns the holdability of the statement > returned by ResultSet.getStatement(). > When a ResultSet is created by a procedure call, its holdability may not > match the holdability of the Statement that called the procedure, which is > probably what ResultSet.getStatement() should return. > This may not be exposed as a bug yet, but I think this method should be > directly obtaining the holdability of the ResultSet using the > Activation.getResultSetHoldability() method, rather than through a Statement. > Seems a safer approach. -- 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
