ID:               36449
 Updated by:       [EMAIL PROTECTED]
 Reported By:      brice dot joly at free dot fr
 Status:           Bogus
 Bug Type:         PDO related
 Operating System: Windows XP
 PHP Version:      5.2.0-dev
 New Comment:

Please read my comments again, carefully.


Previous Comments:
------------------------------------------------------------------------

[2006-04-30 10:43:58] brice dot joly at free dot fr

Some quick clarification: the problem occurs even with non-prepared
code:

$dbh = new PDO('mysql:host=localhost;dbname=test', 'user', 'password',
array(PDO::ATTR_PERSISTENT => true);

foreach ($dbh->query("CALL simpleTest()") as $row) {
    print_r($row);
}
$arr = $dbh->errorInfo();
print_r($arr);

So I'm afraid the problem is not directly linked with the native
prepared statement API, though the people at that conference might know
better.

------------------------------------------------------------------------

[2006-04-30 01:06:53] [EMAIL PROTECTED]

Not a PHP bug; you cannot use CALL with the native prepared statement
API in mySQL.

Use the latest snapshot or PHP 5.1.3 (being released any day now) and
follow the advice in:
http://netevil.org/node.php?nid=795



------------------------------------------------------------------------

[2006-04-27 10:38:38] brice dot joly at free dot fr

Not yet fixed in build of Apr 27 2006 08:15:12, above code still fails.

------------------------------------------------------------------------

[2006-04-17 01:00:01] 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".

------------------------------------------------------------------------

[2006-04-09 07:54:37] [EMAIL PROTECTED]

Please try using this CVS snapshot:

  http://snaps.php.net/php5.1-latest.tar.gz
 
For Windows:
 
  http://snaps.php.net/win32/php5.1-win32-latest.zip

The next snapshot dated after this message likely fixes this.

------------------------------------------------------------------------

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/36449

-- 
Edit this bug report at http://bugs.php.net/?id=36449&edit=1

Reply via email to