[ http://issues.apache.org/jira/browse/DERBY-948?page=comments#action_12368319 ]
Knut Anders Hatlen commented on DERBY-948: ------------------------------------------ Just realized there might be one issue with my implementation of ResultSet.getHoldability() in the embedded driver. To find the holdability, one has to call ResultSet.getStatement().getResultSetHoldability(). However, getStatement() might return null leading to a NullPointerException. It seems like the only way to get a ResultSet which returns null for getStatement() is through EmbedConnectionContext.getResultSet(). What is the holdability of the result sets returned by this method? And can those result sets be exposed to an application, or are they just used internally? > Miscellaneous ResultSet methods added by JDBC 4 > ----------------------------------------------- > > Key: DERBY-948 > URL: http://issues.apache.org/jira/browse/DERBY-948 > Project: Derby > Type: New Feature > Components: JDBC > Reporter: Rick Hillegas > Assignee: Knut Anders Hatlen > Fix For: 10.2.0.0 > Attachments: DERBY-948-v1.diff, DERBY-948-v1.stat, DERBY-948-v2.diff, > DERBY-948-v2.stat > > As described in the JDBC 4 spec sections 16 and 3.1. > This provides support for new ResultSet methods added by JDBC4 and not > addressed by other JIRAs: getHoldability() and isClosed(). -- 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
