Bug #76048 [Opn->Csd]: PDO Mysql max_execution_time is not respected

Edit report at https://bugs.php.net/bug.php?id=76048&edit=1 ID: 76048 Updated by: nikic@php.net Reported by: rishabh dot pugalia at gmail dot com Summary: PDO Mysql max_execution_time is not respected -Status: Open +Status: Closed Type: Bug Package: PDO MySQL Operating System: Mac PHP Version: 7.0.28 -Assigned To: +Assigned To: nikic Block user comment: N Private report: N New Comment: Can't reproduce this on current 7.4/8.0 any more, can reproduce on 7.3. I believe the fix for InnoDB lock errors also covered this case. (Please tell me if you still see this issue on current 7.4/8.0.) Previous Comments: ------------------------------------------------------------------------ [2020-02-25 12:00:57] thijs at keeping dot nl Reproduced using PHP 7.4 on both Ubuntu 18.04.4 and macOS 10.15.3. ------------------------------------------------------------------------ [2019-07-01 06:50:08] Fractalizer at yandex dot ru Is reproducable on PHP 7.2 also. Any chances to have this fixed? ------------------------------------------------------------------------ [2018-06-20 15:56:04] anthony at catsone dot com I'm also running into this issue. 100% reproducible as per the original reporter. ------------------------------------------------------------------------ [2018-03-05 08:32:50] rishabh dot pugalia at gmail dot com Adding "PDO Mysql" to the title. ------------------------------------------------------------------------ [2018-03-05 08:18:53] saurav1991 at gmail dot com When client side prepared statement is used i.e PDO::ATTR_EMULATE_PREPARES => true, the expected error PDOException: SQLSTATE[HY000]: General error: 3024 Query execution was interrupted, maximum statement execution time exceeded is thrown However on using server side prepared statements, this exception is not thrown. Compared with a ruby script using the mysql2 client. The exception is thrown both when server side prepared statement is used and when prepared query is sent to mysql directly. This might have to do with how the prepared statement APIs of libmysqlclient are being used internally. ------------------------------------------------------------------------ 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 https://bugs.php.net/bug.php?id=76048 -- Edit this bug report at https://bugs.php.net/bug.php?id=76048&edit=1