db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Knut Anders Hatlen <Knut.Hat...@Sun.COM>
Subject Re: [jira] Created: (DERBY-1288) Bring Derby into JDBC compliance by supporting executeQuery() on escaped procedure invocations
Date Tue, 09 May 2006 15:12:55 GMT
JIRA is down, so I'm posting this on the list.

What Derby currently does, is

  executeQuery:

    fails whenever a stored procedure is invoked (both embedded and
    client)

  executeUpdate:

    embedded: fails if no result sets are returned, succeeds if one or
    more result sets are returned

    client: succeeds regardless of how many result sets are returned,
    but the return value is invalid (-1) when no result sets are
    returned (it is 0 otherwise)

The way I read the javadoc at http://download.java.net/jdk6/docs/api/,
(1) executeQuery() should fail if the number of result sets returned
is not equal to one, and (2) executeUpdate() should fail if the number
of result sets is not equal to zero, and (3) executeUpdate() should
return 0 if the invocation of the stored procedure was successful. Is
my understanding correct?

-- 
Knut Anders

Mime
View raw message