Bug #7398 Updated: Stored procedure error return values not passed through
| From: | joey@php.net | Date: | Mon, 14 May 2001 17:37:04 +0000 |
| Subject: | Bug #7398 Updated: Stored procedure error return values not passed through | ||
| Groups: | php.dev | ||
| Request: | Send a blank email to php-dev+get-55202@lists.php.net to get a copy of this message | ||
ID: 7398
Updated by: joey
Reported By: uk@dataway.ch
Status: Open
Old-Bug Type: Sybase-ct (ctlib) related
Bug Type: Feature/Change Request
Operating system:
PHP Version: 4.0.3pl1
Assigned To:
Comments:
I have started on a way around this several times, but nothing concrete has formed as of yet.
Previous Comments:
---------------------------------------------------------------------------
[2000-10-23 00:00:31] uk@dataway.ch
When a stored procedure is called by sybase_query() and returns an error value, sybase_query does
not return a false value.
I made a stored procedure:
create proc p_err as return -999
go
Then, from php:
echo sybase_query('EXEC p_err')
returns:
(Resource id #2)
Arguably, this could be considered the correct behaviour; but in any case, there should be a way of
getting at the return value (perhaps a function sybase_status() which returns the value of the last
sybase_query()?). Looking through the source code, the status return is simply discarded.
---------------------------------------------------------------------------
ATTENTION! Do NOT reply to this email!
To reply, use the web interface found at http://bugs.php.net/?id=7398&edit=2