[ http://issues.apache.org/jira/browse/DERBY-1288?page=comments#action_12377849 ]
Daniel John Debrunner commented on DERBY-1288: ---------------------------------------------- Lance Andersen replied on derby-dev > What's the required behavior when a update count or multiple result sets are > returned? the expected behavior would be no different then what u do a Statement object today > If multiple result sets are returned when should any error be thrown, before > the execution starts or once the system detects that multiple result sets are > returned? This would probably be implementation defined depending on the mechanism being used. > Bring Derby into JDBC compliance by supporting executeQuery() on escaped > procedure invocations > ---------------------------------------------------------------------------------------------- > > Key: DERBY-1288 > URL: http://issues.apache.org/jira/browse/DERBY-1288 > Project: Derby > Type: Improvement > Components: JDBC > Versions: 10.2.0.0 > Reporter: Rick Hillegas > Fix For: 10.2.0.0 > > The following statement raises an error in Derby: > statement.executeQuery( "{call foo()}" ); > although this statement works: > statement.executeUpdate( "{call foo()}" ); > According to section 6.4 of the latest draft of the JDBC4 Compliance chapter, > both statements are supposed to work in order to claim Java EE JDBC > Compliance. > We need to bring Derby into compliance by supporting executeQuery() on > escaped procedure invocations. -- 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
