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 Wed, 07 Sep 2005 17:40:31 GMT
    [ http://issues.apache.org/jira/browse/DERBY-211?page=comments#action_12322863 ] 

Daniel John Debrunner commented on DERBY-211:

David, your comment is confusing.  'should return no results with an update count of zero'
, no results means no results, not no ResultSets, an update count that is not -1 is a result.

Thus I would see no results being returned as (and this is what the network client returns):

cs.execute() returns false
cs.getUpdateCount() returns -1

Did you mean 'update count of negative one', as the behaviour you seem to describe is what
that embedded driver does today, while you talk about changing it (to the same thing)?

The embedded driver returns (in this situation)

cs.execute() returns false
cs.getUpdateCount() returns 0

It seems Derby embedded always returns 0 (a single update count result) for statements like
DDL, procedure calls, unless the statement returns ResultSet(s) or a valid update count (INSERT/DELETE/UPDATE).

> 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
>     Versions:
>     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:
For more information on JIRA, see:

View raw message