Bug #11489 Updated: Sybase query result is getting destructed

ID: 11489 User updated by: pwmoosman@aol.com Reported By: pwmoosman@aol.com Status: Feedback Bug Type: Sybase-ct (ctlib) related Operating System: Solaris PHP Version: 4.0.5 New Comment: I was able to reproduce this problem in version 4.0.6. But, I was unable to reproduce it in the current cvs tree. However, after looking at the mysql, and sybase (not sybase_ct) modules. I concluded that adding a reference to the global database connecting should be there. So I modified php_sybase_ct.c Previous Comments: ------------------------------------------------------------------------ [2001-06-28 01:16:27] joey@php.net Cannot reproduce with CVS. ------------------------------------------------------------------------ [2001-06-14 10:15:16] pwmoosman@aol.com The following script produces the following error the second time getAppName/sybase_fetch_row is called. Error (warning): /users/pmoosman/test_data/test1.php(26) : Warning - 3 is not a valid Sybase result resource Script: <?php function getConnect() { $db = sybase_connect('xxxx','yyy','zzz'); return $db; } function getAppName($app_id) { // static $db; $sql = "select name from web_apps where application_id=$app_id"; $db = getconnect(); $result = sybase_query($sql, $db); $row = sybase_fetch_row($result); // sybase_free_result($result); return $row[0]; } getAppName(23); getAppName(23); ?> Note: If I uncomment the "static $db" line, the error (warning) goes away. I ran PHP in a debugger and it looks like the sybase connection is getting destructed when the sybase_query results are getting assigned to "$result". ------------------------------------------------------------------------ Edit this bug report at http://bugs.php.net/?id=11489&edit=1