[jira] Commented: (DERBY-1288) Bring Derby into JDBC compliance by supporting executeQuery() on escaped procedure invocations

[ http://issues.apache.org/jira/browse/DERBY-1288?page=comments#action_12378896 ] Knut Anders Hatlen commented on DERBY-1288: --- I wrote: What Derby currently does, is [...] executeUpdate: embedded: fails if no result sets are returned,

[jira] Commented: (DERBY-1288) Bring Derby into JDBC compliance by supporting executeQuery() on escaped procedure invocations

[ http://issues.apache.org/jira/browse/DERBY-1288?page=comments#action_12378633 ] Knut Anders Hatlen commented on DERBY-1288: --- What Derby currently does, is executeQuery: fails whenever a stored procedure is invoked (both embedded and

JDBC4 compliance question, was: [jira] Commented: (DERBY-1288) Bring Derby into JDBC compliance by supporting executeQuery() on escaped procedure invocations

Hi Lance, I agree with Knut Anders' interpretation of the javadoc for java.sql.Statement. He is investigating how executeQuery() and executeUpdate() should behave when the query text invokes a stored procedure: 1) executeQuery() should raise an error if the procedure does not return

Re: JDBC4 compliance question, was: [jira] Commented: (DERBY-1288) Bring Derby into JDBC compliance by supporting executeQuery() on escaped procedure invocations

Rick Hillegas wrote: Hi Lance, I agree with Knut Anders' interpretation of the javadoc for java.sql.Statement. He is investigating how executeQuery() and executeUpdate() should behave when the query text invokes a stored procedure: 1) executeQuery() should raise an error if the

[jira] Commented: (DERBY-1288) Bring Derby into JDBC compliance by supporting executeQuery() on escaped procedure invocations

[ http://issues.apache.org/jira/browse/DERBY-1288?page=comments#action_12378659 ] Satheesh Bandaram commented on DERBY-1288: -- Knut wrote: What Derby currently does, is executeQuery: fails whenever a stored procedure is invoked (both

[jira] Commented: (DERBY-1288) Bring Derby into JDBC compliance by supporting executeQuery() on escaped procedure invocations

[ http://issues.apache.org/jira/browse/DERBY-1288?page=comments#action_12378720 ] Knut Anders Hatlen commented on DERBY-1288: --- Satheesh Bandaram wrote: What Derby currently does, is executeQuery: fails whenever a stored procedure is

Re: [jira] Commented: (DERBY-1288) Bring Derby into JDBC compliance by supporting executeQuery() on escaped procedure invocations

On 5/9/06, Knut Anders Hatlen (JIRA) derby-dev@db.apache.org wrote: [ http://issues.apache.org/jira/browse/DERBY-1288?page=comments#action_12378720 ] According to DERBY-501, executeQuery works for single ResultSet stored procedure for client, but fails for embedded. Since Rick agreed that fixing

[jira] Commented: (DERBY-1288) Bring Derby into JDBC compliance by supporting executeQuery() on escaped procedure invocations

[ http://issues.apache.org/jira/browse/DERBY-1288?page=comments#action_12377843 ] Daniel John Debrunner commented on DERBY-1288: -- What's the required behavior when a update count or multiple result sets are returned? If multiple result sets

Re: [jira] Commented: (DERBY-1288) Bring Derby into JDBC compliance by supporting executeQuery() on escaped procedure invocations

Daniel John Debrunner (JIRA) wrote: [ http://issues.apache.org/jira/browse/DERBY-1288?page=comments#action_12377843 ] Daniel John Debrunner commented on DERBY-1288: -- What's the required behavior when a update count or multiple result

[jira] Commented: (DERBY-1288) Bring Derby into JDBC compliance by supporting executeQuery() on escaped procedure invocations

[ http://issues.apache.org/jira/browse/DERBY-1288?page=comments#action_12377845 ] Rick Hillegas commented on DERBY-1288: -- Lance says: Just to be clear, this requirement has been part of the J2EE specification since 1999. It is not new. JDBC 4 is

[jira] Commented: (DERBY-1288) Bring Derby into JDBC compliance by supporting executeQuery() on escaped procedure invocations

[ 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

[jira] Commented: (DERBY-1288) Bring Derby into JDBC compliance by supporting executeQuery() on escaped procedure invocations

[ http://issues.apache.org/jira/browse/DERBY-1288?page=comments#action_12377869 ] Satheesh Bandaram commented on DERBY-1288: -- Rick, are you proposing executing only escaped procedures using executeQuery() or ALL SQL procedures? Just wondering why

[jira] Commented: (DERBY-1288) Bring Derby into JDBC compliance by supporting executeQuery() on escaped procedure invocations

[ http://issues.apache.org/jira/browse/DERBY-1288?page=comments#action_12377874 ] Daniel John Debrunner commented on DERBY-1288: -- dan If multiple result sets are returned when should any error be thrown, before the execution starts or once

Re: [jira] Commented: (DERBY-1288) Bring Derby into JDBC compliance by supporting executeQuery() on escaped procedure invocations

Daniel John Debrunner (JIRA) wrote: [ http://issues.apache.org/jira/browse/DERBY-1288?page=comments#action_12377874 ] Daniel John Debrunner commented on DERBY-1288: -- dan If multiple result sets are returned when should any error be

[jira] Commented: (DERBY-1288) Bring Derby into JDBC compliance by supporting executeQuery() on escaped procedure invocations

[ http://issues.apache.org/jira/browse/DERBY-1288?page=comments#action_12377881 ] Rick Hillegas commented on DERBY-1288: -- Hi Satheesh, I agree that fixing this issue will likely fix DERBY-501 also. I am keen to see Lance's response to Dan's further

[jira] Commented: (DERBY-1288) Bring Derby into JDBC compliance by supporting executeQuery() on escaped procedure invocations

[ http://issues.apache.org/jira/browse/DERBY-1288?page=comments#action_12377886 ] Rick Hillegas commented on DERBY-1288: -- Mousing in Lance's response: [ http://issues.apache.org/jira/browse/DERBY-1288?page=comments#action_12377874 ] Daniel