|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #66528 No PDOException or errorCode if database becomes unavailable before PDO::commit
Submitted: 2014-01-21 10:09 UTC Modified: -
Avg. Score:4.7 ± 0.8
Reproduced:18 of 21 (85.7%)
Same Version:6 (33.3%)
Same OS:4 (22.2%)
From: fk at florian-kaiser dot net Assigned:
Status: Open Package: PDO MySQL
PHP Version: 5.5.8 OS: Debian Linux
Private report: No CVE-ID:
View Add Comment Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
You can add a comment by following this link or if you reported this bug, you can edit this bug over here.
Block user comment
Status: Assign to:
Bug Type:
From: fk at florian-kaiser dot net
New email:
PHP Version: OS:


 [2014-01-21 10:09 UTC] fk at florian-kaiser dot net
If the database resource (e.g. the MySQL-Server) becomes unavailable before a PDO::commit(), it emits a warning only, e.g. "MySQL server has gone away" or "Error reading result set's header" and code execution proceeds.

Additionally, neither PDO::errorCode() nor PDO::errorInfo() are set. Inspected just after the warnings both suggest that everything is perfectly fine. This is unacceptable.

I dont really like the handling of that situation at all. Since warnings will only get logged in production mode and code execution proceeds without knowing there actually was an error (happens with PDO::commit() that returns true regardless), this will for sure give some developer lots of headaches. Together with that other bug in PDO::commit(), current implementation makes it _impossible_ to reliably check if a PDO::commit() call failed.

Please note that using PDO::query('commit'); instead of PDO::commit() actually respects PDO::ATTR_ERRMODE and behaves in a more proper way, e.g. if set to PDO::ERRMODE_EXCEPTION actually throws a PDOException and PDO::errorCode/errorInfo will be set accordingly. Warnings though will show regardless (when you're on it, fix that as well, please).
This is the only workaround in current implementations to reliably use transactions with PDOMysql.

A severe interruption like connection loss to database should be treated with the same error handling that is used when establishing the connection. Better still, just do it like PDO::query, honor PDO::ATTR_ERRMODE or throw a PDOException per default. No matter what will be implemented, PDO::errorCode and PDO::errorInfo must be fixed so they reflect errors that occur when using PDO::commit().

Test script:
$dbh = new PDO('mysql:dbname=test;host=;charset=UTF8', 'testuser', '');

// prepare table for test
$dbh->query('DROP TABLE IF EXISTS importantdata');
$dbh->query('create table test.importantdata (a int) engine=innodb');

try {

	$dbh->query('insert into importantdata (a) VALUES (1), (2)');

	sleep(20); // shut down mysql-server

} catch (PDOException $e) {
echo 'I should never get here';

Expected result:
"SQLSTATE[HY000]: General error: 2006 MySQL server has gone away" 
[... Script execution stopped]

Actual result:
Warning: PDO::commit(): MySQL server has gone away in /tmp/test.php on line 16

Warning: PDO::commit(): Error reading result set's header in /tmp/test.php on line 16
    [0] => 00000
    [1] => 
    [2] => 

I should never get here
[... Script execution proceeds]


Add a Patch

Pull Requests

Add a Pull Request

PHP Copyright © 2001-2017 The PHP Group
All rights reserved.
Last updated: Mon Apr 24 15:01:45 2017 UTC