#27764 [Opn->Asn]: Stored Procedure with no result sets doesn't set output params
| From: | iliaa@php.net | Date: | Tue, 30 Mar 2004 13:43:24 +0000 |
| Subject: | #27764 [Opn->Asn]: Stored Procedure with no result sets doesn't set output params | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-57112@lists.php.net to get a copy of this message | ||
ID: 27764
Updated by: iliaa@php.net
Reported By: Jeff dot Leigh at Premconf dot com
-Status: Open
+Status: Assigned
Bug Type: MSSQL related
Operating System: Windows 2000
PHP Version: 4.3.5
-Assigned To:
+Assigned To: fmk
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