5.1.2 using MySQL.

This also appears to be a problem with prepared queries. $stmt->execute() returns false, but no exception is raised. Both $db->errorInfo() and $stmt->errorInfo() show no error (code '00000'). The database log shows the query being prepared, but doesn't show the execution attempt.

$res = $stmt->execute();
echo "<pre>"; var_dump($res, $stmt->errorInfo(), $db->errorInfo()); echo "</pre>";

bool(false)
array(1) {
  [0]=>
  string(5) "00000"
}
array(1) {
  [0]=>
  string(5) "00000"
}

Well, I found the problem with my code.

$stmt->bindValue(':something', $some_array, PDO::PARAM_INT);

Obviously, trying to bind an array as an integer doesn't work too well. Some type of error message/exception would be nice to see though.

Im having the same issue.
PHP version: PHP 5.1.4-pl0-gentoo with Hardening-Patch 0.4.9 (cli) (built: May 16 2006 16:51:09)

I dont think It matters having Hardening Patch.

I have used the following code to test:

<?php
/*bug: 37285*/
try
{
    $pdo          = new PDO('pgsql:dbname=iss-callmanager;user=postgres;password=voip123admin;host=localhost');
    $pdo->setAttribute(PDO::ATTR_ERRMODE, PDO::ERRMODE_EXCEPTION);
    /* the following statement have SQL error, no space between SET value and WHERE clause */
    $statement    = $pdo->prepare('UPDATE patterns SET pattern_name = :pattern_nameWHERE pattern_id = :pattern_id');
    $pattern_name = 'SIP Internas';
    $pattern_id   = 4;
    $values       = array(':pattern_name' => $pattern_name, ':pattern_id' => $pattern_id);
    $result       = $statement->execute($values);
    var_dump($result);
    var_dump($statement->errorInfo());
}
catch ( PDOException $error )
{
    echo $error->getMessage() . "\n"; 
}
?>

I was expecting an exception, or the query executed successfully, nothing happens. I have noticed that postgresql executes the query correctly If I put the literal query in the command line, no matter that no space exists between the SET value and the starting of the WHERE clause.

I am able to reproduce this using the following example:

<?php
    $objDB = new PDO('mysql:dbname=mysql;host=127.0.0.1', 'root', '');

    $objDB->setAttribute(PDO::ATTR_ERRMODE, PDO::ERRMODE_EXCEPTION);

    $objStmt = $objDB->prepare('I do not even remotely resemble a query.');

    $objStmt->execute();
?>

The key in my case is in changing the connection parameters. If I'm connecting to a MySQL 5 server, the exception is thrown correctly. If I'm connecting to a MySQL 4.0 server, no exception is thrown.

At the client end I have MySQL 5 libraries installed, running bundled PDO via PHP 5.2.2.

Please try using this CVS snapshot:

  http://snaps.php.net/php5.2-latest.tar.gz
 
For Windows:

  http://windows.php.net/snapshots/

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".

I have the same bug in 5.3.19 on CentOS when I use dbLib to connect to SQL Server 2008. I get warnings, but blatantly invalid queries don't raise exception, despite setting ATTR_ERRMODE. The attribute is set, but it has no effect.