We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
2.6.2 introduced a BC break when using OPTIMISTIC locking.
See: #7291 (comment)
EntityManager::find() with LockMode LockMode::OPTIMISTIC worked outside of a transaction.
Calling EntityManager::find() with LockMode::OPTIMISTIC outside of a transaction throws a TransactionRequiredException
// In ORM 2.6.2 $entityManager->find(MyEntity::class, $id, \Doctrine\DBAL\LockMode::OPTIMISTIC);
The text was updated successfully, but these errors were encountered:
Functional test for doctrine#7366
f689fda
Fix for doctrine#7366
2394547
Fix for BC break doctrine#7366 when calling EM::find() with LockMode:…
3acfa50
…:OPTIMISTIC outside of a TX
8cec92a
Fixed by #7367, will land in 2.6.3.
Sorry, something went wrong.
ce76688
718134c
Fix for BC break #7366 when calling EM::find() with LockMode::OPTIMIS…
df26f1c
…TIC outside of a TX
Majkl578
No branches or pull requests
BC Break Report
Summary
2.6.2 introduced a BC break when using OPTIMISTIC locking.
See: #7291 (comment)
Previous behavior
EntityManager::find() with LockMode LockMode::OPTIMISTIC worked outside of a transaction.
Current behavior
Calling EntityManager::find() with LockMode::OPTIMISTIC outside of a transaction throws a TransactionRequiredException
How to reproduce
The text was updated successfully, but these errors were encountered: