[ http://issues.apache.org/jira/browse/DERBY-953?page=comments#action_12371424 ]
Daniel John Debrunner commented on DERBY-953: --------------------------------------------- I was expecting the patch to be very similar to the one for ResultSet.isClosed(), but it seems to have gained in complexity for little value. Not sure I understand David's comment about "using exception for mainline decisions", I don't see that happening in the simpler version of the patch (ie. one similar to the changes made for ResultSet.isClosed()). An execption is only used when the Statement is closed, that's not the mainline execution, it's the exception case. Sorry, I wasn't able to comment earlier, I've been busy,. > Add miscellaneous Statement methods introduced by JDBC 4 > -------------------------------------------------------- > > Key: DERBY-953 > URL: http://issues.apache.org/jira/browse/DERBY-953 > Project: Derby > Type: New Feature > Components: JDBC > Reporter: Rick Hillegas > Assignee: Kristian Waagan > Fix For: 10.2.0.0 > Attachments: DERBY-953-1a.diff, DERBY-953-1a.stat, DERBY-953-2a.diff, > DERBY-953-3a.diff > > As described in the JDBC 4 spec, sections 13.1 and 3.1. > This adds support for new Statement methods added by JDBC4 and not addressed > by other JIRAs: isClosed() and getResultSetHoldability(). -- 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
