db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <derby-...@db.apache.org>
Subject [jira] Closed: (DERBY-1314) Differences between client and embedded when invoking stored procedures using Statement.executeUpdate()
Date Fri, 23 Jun 2006 12:24:30 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1314?page=all ]
     
Knut Anders Hatlen closed DERBY-1314:
-------------------------------------

    Fix Version: 10.2.0.0
     Resolution: Fixed

Committed revision 416696.

> 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
>      Fix For: 10.2.0.0
>  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


Mime
View raw message