ID: 22403
User updated by: cesararnold at yahoo dot com dot br
Reported By: cesararnold at yahoo dot com dot br
-Status: Feedback
+Status: Open
Bug Type: Sybase-ct (ctlib) related
Operating System: *
PHP Version: 4CVS, 5CVS
Assigned To: thekid
New Comment:
Congratulations!
It seems to be working now, but not for all cases. Instead of a php
crash and the web server stopped, a "HTTP 500 - Internal server error"
page appears and "The page cannot be displayed". That's fine. But if I
put a "echo " command before the query like the following example, the
php crashes. If the "echo" is removed, the "HTTP 500 ..." error
appears.
...
line 098) echo "Testing ...";
line 099)
line 101) // select data
line 102) $cmd_sql = "exec sp_procedure";
line 103)
line 104) if (DB::isError($query = $db_conn->query($cmd_sql)))
line 105) {
line 106) // get the native backend error
line 107) // and the last query
line 108) exit($query->getMessage());
line 109) }
...
I have two more questions to do about the last update:
- on the last stable version downloaded exists a new folder called
"ext", that seems to be similat to "extensions". Now we have 2 folders
on php directory, with similar dlls. Is that correct ?
- why it does not execute the "exit" command at line 108, because (in
my oppinion) a error is occuring at the sql command ? is that error
code returned or not ?
It seems that you are almost arriving to solve the case.
Anything alse we can do to help, please advise.
Thanks for all your help.
Previous Comments:
------------------------------------------------------------------------
[2004-01-23 21:38:34] [EMAIL PROTECTED]
Please try using this CVS snapshot:
http://snaps.php.net/php5-latest.tar.gz
For Windows:
http://snaps.php.net/win32/php5-win32-latest.zip
------------------------------------------------------------------------
[2004-01-19 07:34:29] cesararnold at yahoo dot com dot br
I´m sorry.
I´m not a php developer and wouldn´t get access to php "c" code.
Is there a patch available on php.net ?
Thanks.
------------------------------------------------------------------------
[2004-01-18 12:01:27] [EMAIL PROTECTED]
Please try out the patch available at
http://sitten-polizei.de/php/bug_22403.patch
This should fix it.
------------------------------------------------------------------------
[2003-07-15 07:28:49] daniel dot beet at accuratesoftware dot com
I am experiencing crashes with Apache 1.3.26, IBM HTTP (1.3.19.5) & IIS
5, PHP 4.3.2 & Sybase 12.5 on Windows 2000.
This occurs when executing a stored procedure, but when the user does
not have execute privilages.
I get the following error in the error log:
PHP Warning: sybase_query(): Sybase: Server message: EXECUTE
permission denied on object <STORED_PROC>, database <DATABASE>, owner
dbo
(severity 14, procedure <STORED_PROC>) in
c:\cvsdata\test\test_db_connection.php on line 177
Then the webserver crashes & restarts. This is not ideal.
Line 177 has the function sybase_query()
If I change the query to a SP that the user does have execute
privilages on, everything works OK. If I cause a deliberate error such
as execution a SP that does not exist, the error is returned as normal
with no crash.
Has anyone else seen this behaviour?
------------------------------------------------------------------------
[2003-06-02 14:58:46] cesararnold at yahoo dot com dot br
Hi,
we still waiting for the fix.
Sometimes we must restart the web server and this is causing some
problems to the users and mainly for our customers. What to say to the
customers when web server stops sometimes regarding a php error ?
I got more info if can help.
The problem happens not only when the procedure receives null
parameters for non null arguments.
If, in a procedure code, for example, I create a temporary table and it
have fields that does not accept null values and, when inserting rows
with null values into non null fields, the same problem happens. PHP
stops the web server. Sybase just returns error (-6) advising that the
field does not accept null values ...
We know that this is a error on the logics of the procedure and can be
fixed by the programmer, fixing the code and recompiling the procedure
and so on.
We know that you are doing the best, but on my single oppinion, it's a
problem to be fixed urgently.
Are there any news about this bug fix ?
Thanks again.
------------------------------------------------------------------------
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/22403
--
Edit this bug report at http://bugs.php.net/?id=22403&edit=1
