ID: 42548
Comment by: al dot smith at aeschi dot ch dot eu dot org
Reported By: garethjo at usc dot edu
Status: Assigned
Bug Type: MySQLi related
Operating System: Windows XP, Windows 2003
PHP Version: 5.2.4
Assigned To: georg
New Comment:
$query = "CALL count_runs(".$row["id"].", ".$minyear.",
".$maxyear.")";
$db->multi_query($query) or die ("Error in query: $query. " .
$db->error);
This was my query.
Previous Comments:
------------------------------------------------------------------------
[2007-09-11 15:54:04] garethjo at usc dot edu
No it doesn't, I tried it with both before sending in the bug report.
------------------------------------------------------------------------
[2007-09-11 10:00:30] uwendel at mysql dot com
Does using mysqli_multi_query() work for you? Currently you are using
mysqli_real_query() to call the SP. See also,
http://dev.mysql.com/doc/refman/5.1/en/call.html. If a stored procedure
produces result sets, you must use mysqli_multi_query().
Ulf
------------------------------------------------------------------------
[2007-09-09 10:42:13] [EMAIL PROTECTED]
Georg (or whoever maintains mysqli nowadays), check this out. Seems
like some regression bug between 5.2.3 / 5.2.4 crept in..
------------------------------------------------------------------------
[2007-09-07 18:00:17] al dot smith at aeschi dot ch dot eu dot org
I'm seeing this exact bug as well. Rolling back to 5.2.3 fixes the
problem.
For me, executing the CALL() statement within a mysql> client session
works just fine...
------------------------------------------------------------------------
[2007-09-07 14:50:18] garethjo at usc dot edu
Yes I have seen those bugs and they are not what I am experiencing. Any
stored procedure that would normally return a resultset whether it be
the first or not produces the "PROCEDURE procedure.Name can't return a
result set in the given context" error not a lost connection. In my
example code, the first query is just used to create the database table
and stored procedure. So even if it is separated out and ran separately
so that the bug test is in a separate file and runs by itself after the
database tables and proc are created, it will still produce the same
result even though it is the first proc that was run.
------------------------------------------------------------------------
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/42548
--
Edit this bug report at http://bugs.php.net/?id=42548&edit=1
