Skip to content
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

Merge origin/3.9.x up into 4.2.x #6587

Merged
merged 3 commits into from
Nov 5, 2024
Merged

Merge origin/3.9.x up into 4.2.x #6587

merged 3 commits into from
Nov 5, 2024

Conversation

greg0ire
Copy link
Member

@greg0ire greg0ire commented Nov 5, 2024

The conflict is completely ignored in favor of #6546

$ git merge -s ours origin/3.9.x
Merge made by the 'ours' strategy.

simPod and others added 3 commits November 2, 2024 18:29
… transaction

Let's get rid of There's no active transaction exception which occurs e.g. when using deferred constraints so the violation is checked at the end of the transaction and not during it.

- Do not rollback only on exceptions where we know the transaction is no longer active
- Introduce TransactionRolledBack exception
- Transform Oracle's "transaction rolled back" exception and use the underlying one that DBAL supports
Fix incorrect `transactional()` handling when DB auto-rolled back the transaction
@greg0ire greg0ire merged commit 9a3d08d into doctrine:4.2.x Nov 5, 2024
3 checks passed
@greg0ire greg0ire changed the title 4.2.x Merge origin/3.9.x up into 4.2.x Nov 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants