#38842 [Opn]: PDO nextRowset not working on MySQL

ID: 38842 Updated by: uw@php.net Reported By: stochnagara at hotmail dot com Status: Open Bug Type: Feature/Change Request Operating System: windows xp PHP Version: 5CVS-2006-09-15 (snap) New Comment: Wait for PDO_MYSQLND and try again. Should be fixed. Note that multi-statement contradicts the PDO idea of a "secure" driver. Enabling multi-statement by default means opening all doors for SQL injections! Previous Comments: ------------------------------------------------------------------------ [2006-12-04 17:45:05] mike at we11er dot co dot uk Anyone? ------------------------------------------------------------------------ [2006-10-17 16:04:50] mike at we11er dot co dot uk Err, sorry... that last error should be: PDOStatement::execute() [function.PDOStatement-execute]: SQLSTATE[HY000]: General error: 2013 Lost connection to MySQL server during query ------------------------------------------------------------------------ [2006-10-17 16:03:32] mike at we11er dot co dot uk IMO this is a bug. If a stored procedure is called, it returns multiple row sets, one for each query inside it that returns results, and one for the return status. Because all the results from a statement must be fetched before subsequent statements can be made, we NEED nextRowset to work otherwise the following error is received: PDOStatement::nextRowset() [function.PDOStatement-nextRowset]: SQLSTATE[HYC00]: Optional feature not implemented closeCursor() does not work when multiple rowsets are present. ------------------------------------------------------------------------ [2006-09-18 07:35:53] tony2001@php.net "Optional feature not implemented" means this functionality is not yet available. Which in turn means it's feature request. ------------------------------------------------------------------------ [2006-09-18 06:35:02] stochnagara at hotmail dot com Sorry, this is not a feature request but a PDO related bug. ------------------------------------------------------------------------ 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/38842 -- Edit this bug report at http://bugs.php.net/?id=38842&edit=1