ZF-3343: fetchRow no longer working after revision 9539
Description
After getting lastest svn trunk I got the exception:
Fatal error: Uncaught exception 'Zend_Db_Statement_Exception' with message 'SQLSTATE[HYC00]: Optional feature not implemented' in R:\library\Zend\Db\Statement\Pdo.php:167 Stack trace:
0 R:\library\Zend\Db\Adapter\Abstract.php(637): Zend_Db_Statement_Pdo->closeCursor()
1 C:\My Docs\My Source Code\SVN\vproject\library\Zion\Db\Row\Abstract.php(109): Zend_Db_Adapter_Abstract->fetchRow(Object(Zend_Db_Select))
2 C:\My Docs\My Source Code\SVN\vproject\library\Zion\Db\Row\Abstract.php(406): Zion_Db_Row_Abstract->_load(Array)
3 [internal function]: Zion_Db_Row_Abstract->__call('load', Array)
4 C:\My Docs\My Source Code\SVN\vproject\application\controllers\IndexController.php(51): Album->load(4912640)
5 R:\library\Zend\Controller\Action.php(502): IndexController->indexAction()
6 R:\library\Zend\Controller\Dispatcher\Standard.php(293): Zend_Controller_Action->dispatch('indexAction')
7 R:\library\Zend\Controller\Front.php(914): Zend_Controller_Dispatcher_Standard->dispatch(Object(Zend_Controller_Request_Http), Object(Zend_Con in R:\library\Zend\Db\Statement\Pdo.php on line 167
Checking out the error I found that in issue 2101 there was a change done (http://framework.zend.com/code/browse/…), this change generates the problem, after commenting the line:
//while ($this->_stmt->nextRowset()) {}
the problem was solved.
Comments
Posted by Aldemar Bernal (aldemar.bernal) on 2008-05-28T13:31:14.000+0000
This issue is based on the solution that was given to issue ZF-2101
Posted by Aldemar Bernal (aldemar.bernal) on 2008-05-28T13:33:06.000+0000
Hi Simon, you resolved ZF-2101, I guess you know how to solve this
Posted by julien PAULI (doctorrock83) on 2008-05-29T11:46:40.000+0000
You should have a look at the comment for the nextRowset() method in PHP Doc http:/www.php.net/pdostatement.nextrowset
Perhaps that bug as well ? http://bugs.php.net/bug.php?id=41997
Posted by Simon Mundy (peptolab) on 2008-05-29T15:30:45.000+0000
Reverted the original commit that caused this problem. Will look into a more consistent fix.