[ http://issues.apache.org/jira/browse/DERBY-1314?page=all ]
Knut Anders Hatlen updated DERBY-1314:
--------------------------------------
Attachment: derby-1314-v1.diff
derby-1314-v1.stat
The attached patch fixes the issue on the client. When executeUpdate() is used
to invoke a stored procedure, an update count of -1 (indicating that no update
count is returned) is changed to 0, as the javadoc for executeUpdate() says.
With this patch, four more of the test cases in jdbcapi/ProcedureTest.junit
succeed with the client driver (but the test will not be enabled until the
patch for DERBY-501 is checked in).
executeUpdate() on the embedded driver will be fixed as part of DERBY-501.
Derbyall didn't show any failures with the patch. Please review. Thanks!
> Differences between client and embedded when invoking stored procedures using
> Statement.executeUpdate()
> -------------------------------------------------------------------------------------------------------
>
> Key: DERBY-1314
> URL: http://issues.apache.org/jira/browse/DERBY-1314
> Project: Derby
> Type: Bug
> Components: JDBC
> Versions: 10.2.0.0
> Reporter: Knut Anders Hatlen
> Assignee: Knut Anders Hatlen
> Attachments: derby-1314-v1.diff, derby-1314-v1.stat
>
> When invoking a stored procedure using Statement.executeUpdate(), the
> client driver and the embedded driver behave differently.
> If the stored procedure does not return any result set, the embedded
> driver returns 0, whereas the client returns -1.
> If the stored procedure returns one or more result sets, the embedded
> driver returns -1, whereas the client fails with an exception.
--
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
