[ http://issues.apache.org/jira/browse/DERBY-1314?page=all ]
Knut Anders Hatlen updated DERBY-1314:
--------------------------------------
Derby Info: [Patch Available, Release Note Needed]
Proposal for release note (DERBY-501 and DERBY-1314):
The behaviour of executeQuery() and executeUpdate() has been modified
to follow the JDBC standard when executing stored procedures. For the
embedded driver, this means that
a) it is now possible to use executeQuery() to execute a stored
procedure that returns exactly one ResultSet (this would fail in
previous releases of Derby)
b) executeUpdate() will raise an exception if it is used to execute
a stored procedure that returns one or more ResultSets (this
would succeed in previous releases of Derby)
For the client driver, the following has changed:
a) PreparedStatement.executeUpdate() will raise an exception if it
is used to execute a stored procedure that returns one or more
ResultSets (previously, it would succeed, whereas Statement and
CallableStatement correctly raised an exception)
b) executeUpdate() will return 0 when executing a stored procedure
which doesn't return a ResultSet (previously it would return -1)
> 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
