ID: 1441 Comment by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: Closed Bug Type: Sybase-ct (ctlib) related Operating System: Linux Redhat 5.2 PHP Version: 4.0 New Comment:
ver 4.2.2 this behavior is still there Previous Comments: ------------------------------------------------------------------------ [2001-02-10 13:20:30] [EMAIL PROTECTED] looks to me like 4.0 should handle this correctly. ------------------------------------------------------------------------ [1999-12-13 16:12:20] [EMAIL PROTECTED] While I can confirm that the behavior is still there, I am moving it to a feature/change request. It'd be nice, though.... ------------------------------------------------------------------------ [1999-05-23 20:56:11] [EMAIL PROTECTED] Follow this procedure to reproduce the problem: - Use sybase_pconnect() a few times to start up a few persistent connections. - Start Sybase Central and kill off the PHP3 connections. - Rerun the script that uses sybase_pconnect(). sybase_pconnect() will NOT fail, however any following sybase_query() will return 0, but no other error message. Looks like PHP3 tries to run the query on a persistent connection that has disappeared, but doesn't fail in sybase_pconnect() as it should. Ideally, it should check if a persistant connection is gone and not fail at all, but if it have to fail it should do it in the "right" function :-) ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=1441&edit=1
