db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-211) Network Server returns no result sets for a procedure call that returns no result
Date Thu, 30 Mar 2006 00:48:36 GMT
    [ http://issues.apache.org/jira/browse/DERBY-211?page=comments#action_12372347 ] 

Daniel John Debrunner commented on DERBY-211:
---------------------------------------------

13.3.3.2 JDBC 4.0 (CallableStatement.executeUpdate) has not changed from JDBC 3.0's 13.3.3
section
for CallableStatement., I was looking at the PreparedStatement section in JDBC 3.0 by mistake.

Section 13.3.3.2 JDBC 4.0 (CallableStatement.executeUpdate) and JDBC 3.0's 13.3.3 sections
do seem to be in conflict with the javadoc for PreparedStatement..executeUpdate.
(No override of executeUpdate exists in CallableStatement).

> Network Server returns no result sets for a procedure call that returns no result
> ---------------------------------------------------------------------------------
>
>          Key: DERBY-211
>          URL: http://issues.apache.org/jira/browse/DERBY-211
>      Project: Derby
>         Type: Bug
>   Components: Network Server, Newcomer
>     Versions: 10.1.1.0
>     Reporter: Kathey Marsden

>
> For a call of a procedure with no dynamic results embedded 
> Cloudscape returns a one result, an update count of zero.  However, using the network
server no results are returned. We should be consistent.
> To reproduce 
> See call za() in lang/procedure.java test.

-- 
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


Mime
View raw message