-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Commits silently fail (Percona cluster + Galera plugin) #7893
Comments
@Hamael18 thanks. This seems to be an easy thing to solve and to isolate in a unit test. |
@lcobucci Unfortunately this needs to be moved to 2.7, since it requires a bump in the doctrine/dbal version from ^2.6 to ^2.10 and we're not able to do this on a patch level release. I'm moving this to 2.7, which can tolerate dependency bumps like the required one here, and we can work on a quick/simple patch after we have 2.6.5 out of the door. |
if (!$conn->commit()) {
throw new OptimisticLockException('Commit failed', $entity);
}
} catch (Throwable $e) {
$this->em->close();
if ($conn->isTransactionActive()) {
$conn->rollBack();
} Small proposal for UnitOfWork::commit() |
@chosroes thanks! |
I'm moving this to version 2.8.0 because DBAL requires PHP 7.2+ and we'll release 2.7.0 still supporting PHP 7.1+. |
Looks like this should have been closed by 1da002c? |
Yes, fixed by #7946 |
Bug Report
Summary
DBAL have been recently updated. It's now 2.10 (doctrine/dbal#3588).
It fix issue with the commit() method. But it's not handled in ORM.
Current behavior
If commit() fails without exception (commit() return false but no exception), there is no information about that.
Expected behavior
Throw an exception if commit() fails and return false.
The text was updated successfully, but these errors were encountered: