Try the latest 5.1.x snapshot from http://snaps.php.net

Hi.  I've tried the latest extensions of PDO and PDO_MYSQL from the latest snapshot and run my php script both on command line and on web.  It still returns garbled output.  Does it do the same for you?

This works with mysqli but not with PDO-MYSQL.  Here is a link to the mysql bug report.

http://bugs.mysql.com/bug.php?id=19008

It doesn't work with the latest snapshot of PDO and PDO-MYSQL.

I can reproduce this issue, for an example output look at: http://bugs.mysql.com/file.php?id=3335 

It has nothing to do with mysql I think, because it works fine with ext/mysqli and mysql commandline client.

If I replace 

$stm = $dbh->prepare('CALL dummy()');
$stm->execute();

with

$stm = $dbh->query('CALL dummy()');

I get exactly the same output. This is not limited to this special stored procedure, happens with every SP I tried!

If I try it on my terminal, I get Array entries like that:

198 =>
  ▒⎼⎼▒≤ (
    'V▒⎼␋▒␉┌␊ ┼▒└␊' => NULL,
    0 => NULL,
    'V▒┌┤␊' => '└␊␍ └┤├␊│␊⎽OFF%⎽┤├50┌/└≤⎽─┌5.⎽⎺␌┐┼␍␊├⎽/?0?KϬ????␍␉114450 2',
    1 => '└␊␍ └┤├␊│␊⎽OFF%⎽┤├50┌/└≤⎽─┌5.⎽⎺␌┐┼␍␊├⎽/?0?KϬ????␍␉114450 2',
  ),

I tested with php5.1-200604091030 snapshot.

(you only need a MySQL 5 DB to reproduce this, no tables needed for this SP...)

I've tried the full latest php snapshot just now and the problem is still there.

Sounds like something is causing the mysql client to convert the data into another character set.
Please check related options and environmental variables that apply.

Hi.  This works with mysqli but not with pdo-mysql.  I've spent 24 hours trying every different variation in both /etc/mysql/my.cnf and setting charsets and collations using SET queries through PDO and nothing has resolved this issue.  Try and see if you can reproduce it.  Everyone I've asked to reproduce this problem has been able to on Linux.  Even on this bug two people have reported the same issue.  The mysql command line and the mysql query browser return correct results and as mentioned previously mysqli also returns the correct output.  It is only PDO_MySQL.  Kindly investigate.   Many thanks for your help.

The other thing that says to me that the problem is not charset related is that this only happens when there is a prepare inside the stored procedure.  If you do a straight select inside an SP that works.  If you do a prepare in PDO and do a select without an SP that works.  However, if you do a prepare inside an SP that doesn't work with pdo_mysql although does work with cmd line mysql, query browser and mysqli.

This appears to be another situation where mysql gives back bogus values for the column lengths when using native prepared statements.

The suggested workaround using the current snapshot is to turn on the PDO prepared statement emulator:

$db = new PDO('mysql:dbname=test', 'root', '');
$db->setAttribute(PDO::ATTR_ERRMODE,PDO::ERRMODE_EXCEPTION);
$db->setAttribute(PDO::ATTR_EMULATE_PREPARES, true);
$stm = $db->prepare('CALL dummy()');
$stm->execute();
var_dump($stm->fetchAll());

This script reproduces the problem using mysqli:

$db = new mysqli("localhost", "root", "", "test");

$stmt = $db->stmt_init();
if ($stmt->prepare("CALL dummy()")) {
    $stmt->execute();
    $stmt->bind_result($name, $value);
    while ($stmt->fetch()) {
        echo $name, " ", $value, "\n";
    }
}

This is a mysql client library bug.

This is NOT a bogus bug, and I am not certain that it is in the MySQL codebase at all.

I think it is likely PHP based, as if I use the SQLyog mysql GUI client to call the stored procedure in question, there are no problems displaying the results, but if I use PHP in any form to manipulate/show the results, it's all garbled.

The reason WHY I need to use prepared statements inside of a stored procedure?  See this bug here:

http://bugs.mysql.com/bug.php?id=11918

Hey guys!

I'm using Zend Framework and facing the same problem. Somewhere in the deep Internet I found how to disable use of PREPARE statements by PDO MySQL. 

(works for me)
$db->setAttribute(PDO::MYSQL_ATTR_DIRECT_QUERY, 1);

This helps because of this:

http://shayanzadeh.com/2007/02/08/stored-procedures-with-dynamic-queries-in-mysql-through-php/

Closing.