Description:
------------
When interacting with a PDOStatement object, the consumer should be able to expect all exceptions to be reported as PDOException. However, in certain cases, the extension leaks its internal implementation details and throws an Error.

Test script:
---------------
<?php

$conn = new PDO('sqlite:memory:');
$stmt = $conn->prepare('SELECT ?');

$stmt->bindValue(1, new DateTime());

try {
    $stmt->bindValue(1, new DateTime());
} catch (Throwable $e) {
    echo get_class($e), ': ', $e->getMessage(), PHP_EOL;
}

try {
    $stmt->execute([new DateTime()]);
} catch (Throwable $e) {
    echo get_class($e), ': ', $e->getMessage(), PHP_EOL;
}

// the above seems to be implemented just by casting the value to a string since it behaves exactly as the following:

try {
    (string) (new DateTime());
} catch (Throwable $e) {
    echo get_class($e), ': ', $e->getMessage(), PHP_EOL;
}


Expected result:
----------------
A PDOException is thrown instead of an Error

PDOException: Some message that says that this type cannot be bound to the statement


Actual result:
--------------
Error: Object of class DateTime could not be converted to string