The IBM DB2 Statement driver suppresses errors triggered by db2_execute

[morozov]

db2_execute() can trigger different kinds of errors internally:

1. A notice:

   $stmt = $conn->executeQuery('SELECT * FROM users WHERE user_name = ?', [[]]);

   Expected result:

   Notice: Array to string conversion in lib/Doctrine/DBAL/Driver/IBMDB2/DB2Statement.php on line 175
   

   Actual result: nothing. The error is suppressed.
2. A catchable fatal error:

   $stmt = $conn->executeQuery('SELECT * FROM users WHERE user_name = ?', [new stdClass()]);

   Expected result:

   Catchable fatal error: Object of class stdClass could not be converted to string in lib/Doctrine/DBAL/Driver/IBMDB2/DB2Statement.php on line 175
   

   Actual result: nothing. The script silently exists.

Neither of the errors above seems to be needed/possible to handle on the DBAL level. The first one doesn't make db2_execute() return FALSE, the other cannot be caught using a try/catch block.

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.