Transaction remains open after PDO query timeout in Phalcon 5.x

Answer

No. Phalcon 5.x does not automatically roll back a transaction when a PDO statement exceeds PDO::ATTR_TIMEOUT. The driver throws an exception, but the transaction context remains open until your application explicitly rolls it back or the connection ends.

Confirmed facts and assumptions

This behavior applies to Phalcon 5.x database adapters built on PDO. The framework does not treat statement timeouts as fatal transaction errors. Version assumption: Phalcon 5.x stable releases. Do not assume this applies to other major versions without testing.

Steps for this case

1. Wrap transactional code in try/catch.
2. Catch PDOException after the timeout.
3. Call $connection->rollback() in the catch block.
4. Re-throw, log, or return an error as appropriate for your application.

$connection->begin();
try {
    $connection->execute('UPDATE ...');
    $connection->commit();
} catch (PDOException $e) {
    $connection->rollback();
    throw $e;
}

Driver portability

MySQL and PostgreSQL generally leave the transaction open after a statement timeout. SQLite may roll back on some fatal errors, but this is not guaranteed across versions. For portable Phalcon code, assume the transaction is open after any PDO exception and roll back explicitly for every driver.

Verification

Run a deliberately long query with PDO::ATTR_TIMEOUT set to a few seconds, catch the exception, then attempt another statement on the same connection. If it executes without error, the transaction is likely still open.

Which PDO driver are you using? SQLite-specific rollback behavior may need separate verification.