Req #7398 [Opn->Wfx]: Stored procedure error return values not passed through
| From: | krakjoe@php.net | Date: | Tue, 17 Feb 2015 08:02:57 +0000 |
| Subject: | Req #7398 [Opn->Wfx]: Stored procedure error return values not passed through | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-190729@lists.php.net to get a copy of this message | ||
Edit report at https://bugs.php.net/bug.php?id=7398&edit=1
ID: 7398
Updated by: krakjoe@php.net
Reported by: uk at dataway dot ch
Summary: Stored procedure error return values not passed
through
-Status: Open
+Status: Wont fix
Type: Feature/Change Request
Package: Sybase-ct (ctlib) related
Operating System: Linux 2.2.17
PHP Version: 4.0.3pl1
Block user comment: N
Private report: N
New Comment:
I'm going to mark as won't fix.
Sybase has been removed in PHP7 because it doesn't have a user base in 5.
If in the future a maintainer for the extension pops up and decides to deploy sybase with PECL, they
can always use the bug search feature here to find this report.
Sorry about the wait.
Previous Comments:
------------------------------------------------------------------------
[2001-05-14 13:37:04] joey@php.net
I have started on a way around this several times, but nothing concrete has formed as of yet.
------------------------------------------------------------------------
[2000-10-23 00:00:31] uk at dataway dot 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.
------------------------------------------------------------------------
--
Edit this bug report at https://bugs.php.net/bug.php?id=7398&edit=1