Bug #14354 Updated: sybase_query returns 1 regardless of delete success
| From: | mheumann at sei dot cl | Date: | Tue, 08 Jan 2002 22:02:44 +0000 |
| Subject: | Bug #14354 Updated: sybase_query returns 1 regardless of delete success | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-76288@lists.php.net to get a copy of this message | ||
ID: 14354
User updated by: mheumann@sei.cl
Reported By: mheumann@sei.cl
Old Status: Feedback
Status: Open
Bug Type: Sybase (dblib) related
Operating System: Linux Mandrake 8
PHP Version: 4.0.6
New Comment:
I just tried it on php 4.1.1 and the problem still exists.
Previous Comments:
------------------------------------------------------------------------
[2002-01-07 02:34:06] lobbin@php.net
Does this problem still exist on 4.1.1?
------------------------------------------------------------------------
[2001-12-12 06:41:44] derick@php.net
oh, ok, then it is not bogus.
------------------------------------------------------------------------
[2001-12-12 06:24:21] mheumann@sei.cl
I'm not sure if I can agree with you on that. If I don't use the @ sign,
sybase_query displays a warning of the type
Warning: Sybase message: Children still exist in 'table1'. Cannot delete
parent 'table2'. (severity 16) in /path/to/my/script.php on line 1432
Doesn't that mean that sybase_query didn't return ok?
Besides, according to the documentation, the function
sybase_affected_rows is only implemented for the ct library, not dblib.
Unfortunately, we haven't been able to get sybase-ct to work for us,
even though we tried all the hints we could get.
------------------------------------------------------------------------
[2001-12-11 13:58:59] derick@php.net
Actually, this is not a bug. The query still executes ok, but the result
is different then you want. You can check with the sybase_affected_rows
function if it is deleted or not:
www.php.net/sybase_affected_rows
Derick
------------------------------------------------------------------------
[2001-12-11 07:36:16] mheumann@sei.cl
Hello? Anybody home? I kinda need this problem to be solved, please.
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/?id=14354
Edit this bug report at http://bugs.php.net/?id=14354&edit=1