[
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, 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)
This wasn't correct either... :(
It should have said:
executeUpdate:
Embedded: Succeeds regardless of how many result sets are
returned. Returns 0 if no result sets are returned, -1 if one or
more result sets are returned.
Client: Succeeds and returns -1 when no result sets are
returned. Fails when one or more result sets are returned.
> 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
> Assignee: Knut Anders Hatlen
>
> 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
