ID: 27764 Updated by: [EMAIL PROTECTED] Reported By: Jeff dot Leigh at Premconf dot com -Status: Assigned +Status: Closed Bug Type: MSSQL related Operating System: Windows 2000 PHP Version: 4.3.5 Assigned To: fmk New Comment:
This bug has been fixed in CVS. Snapshots of the sources are packaged every three hours; this change will be in the next snapshot. You can grab the snapshot at http://snaps.php.net/. Thank you for the report, and for helping us make PHP better. The second parameter to mssql_execute() can be used to skip any result sets returned by the stored procedure. I've tested thsi with both php4 and php5 and the parameter works fine, and can even be used as a workarround for this bug. Previous Comments: ------------------------------------------------------------------------ [2004-03-29 17:30:11] Jeff dot Leigh at Premconf dot com Description: ------------ Create an MSSQL stored procedure that does not return any result sets. It only takes input parameters, and returns parameters. Create php code to called stored procedure, bind, etc, etc. Execute the procedure. You will not get any bug reported, and the output param variables will not be changed. mssql_execute will not return anything, since there are no result sets. Thus, 'mssql_next_result' cannot be called. If I force the stored procedure to return at least one result set, the output parameter is set properly. (There is nothing wrong with my MSSQL configuration from what I can tell. I can connect and do standard queries just fine.) Oh, and the current documentation says there is an optional second parameter for mssql_execute()... a boolean. If I try to use it, I get an error regarding an incorrect number of arguments to mssql_execute(). I'm assuming this was depreciated, but not documented. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=27764&edit=1
