ID: 37399 Comment by: jplock at gmail dot com Reported By: aranna at free dot fr Status: Assigned Bug Type: Sybase-ct (ctlib) related Operating System: REH3 PHP Version: 5.1.4 Assigned To: fmk New Comment:
In my case, this is happening with mssql compiled to FreeTDS as well. Previous Comments: ------------------------------------------------------------------------ [2006-05-16 09:15:51] aranna at free dot fr Note this is Sybase not Mssql ------------------------------------------------------------------------ [2006-05-16 06:29:49] [EMAIL PROTECTED] Assigned to the maintainer. ------------------------------------------------------------------------ [2006-05-16 03:00:42] jplock at gmail dot com Ok, more testing, after reverting to PHP 5.1.2 version of ext/mssql (still using PHP 5.1.4), our stored procedure calls work properly again. Something with those dbcancel() calls messes up mssql_next_result(), unfortunately. ------------------------------------------------------------------------ [2006-05-16 02:54:14] jplock at gmail dot com http://cvs.php.net/viewcvs.cgi/php-src/ext/mssql/php_mssql.c?r1=1.152.2.12&r2=1.152.2.13&pathrev=PHP_5_1 In between those differences, a dbcancel(mssql_ptr->link); was added on line 1237 of php_mssql.c. In my case, we're executing a stored procedure which returns five different result sets. One of those result sets calls another stored procedure, which is failing because we're passing in a null value (its suppose to be a real value from the first stored procedure call), and is generate a "query failed" error. Could that 2nd "query failed" error be terminating the link and all of the previous result sets? ------------------------------------------------------------------------ [2006-05-16 01:13:13] jplock at gmail dot com This used to work for us using FreeTDS 0.63 on Solaris 9 with PHP 5.1.2, but after upgrading to PHP 5.1.4, we can not retrieve multiple result sets back using mssql_next_result(), it always returns false. ------------------------------------------------------------------------ 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/37399 -- Edit this bug report at http://bugs.php.net/?id=37399&edit=1
