ID: 35793
Comment by: richard at phase dot org
Reported By: deadman_great at mail dot ru
Status: No Feedback
Bug Type: PDO related
Operating System: RH Fedora Core 2
PHP Version: 5CVS-2005-12-25 (snap)
Assigned To: Wez
New Comment:
$this->pdo->setAttribute(PDO::ATTR_EMULATE_PREPARES, true);
(a suggested fix above) fails on 5.2.RC6 as PDO::ATTR_EMULATE_PREPARES
appears no longer to be defined.
Previous Comments:
------------------------------------------------------------------------
[2006-10-17 01:15:58] michal dot vrchota at seznam dot cz
I think I have solved this problem:
You have to free your PDOStatement instance
Of course You have to call closeCursor() method to be sure, but if you
have more queries and still using same identifier ($stmt) you have free
it by passing NULL value
Sample:
$stmt->closeCursor();
$stmt = NULL;
// now it works ;)
------------------------------------------------------------------------
[2006-10-16 14:46:09] andiesPostfach at web dot de
The Problem still exists in PHP 5.2 RC5 !!
System ist SUSE-Linux 9.3
MySQL Version 5.0.18
------------------------------------------------------------------------
[2006-08-23 11:14:46] tjerk dot meesters at gmail dot com
This problem still occurs with:
PHP-5.1.5
MySQL-5.0.22
Linux platform
Using PDO::ATTR_EMULATE_PREPARES doesn't resolve the problem, the error
message remains:
SQLSTATE[HY000]: General error: 2050 Row retrieval was canceled by
mysql_stmt_close() call
------------------------------------------------------------------------
[2006-08-01 20:52:55] mass at carlsoft dot net
Can we at least change this error message to be more specific, perhaps
suggesting to emulate prepares (as wez @ php . net suggested)? or
better yet make the emulation default?
------------------------------------------------------------------------
[2006-05-07 01:00:00] php-bugs at lists dot php dot net
No feedback was provided for this bug for over a week, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
------------------------------------------------------------------------
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/35793
--
Edit this bug report at http://bugs.php.net/?id=35793&edit=1
