EF Core DbTransaction - Undocumented IDisposable behaviour on Transactions

[RiversJohn]

Type of issue

Missing information

Description

I tried looking for documentation on what the behaviour of a transaction is when it goes out of scope in the following scenarios:

• When commit is called but the action fails, e.g. illegal transaction and throws an exception
• Commit is never called and the transaction simply goes out of scope
• I've assumed that the transaction failing and being disposed results in some kind of implicit RollBackAsync behaviour
• Additionally the usages of RollbackAsync aren't particularly clear

Page URL

https://learn.microsoft.com/en-us/ef/core/saving/transactions

Content source URL

https://github.com/dotnet/EntityFramework.Docs/blob/main/entity-framework/core/saving/transactions.md

Document Version Independent Id

cf56babd-def0-d76e-8eee-e33341b6a009

Article author

@roji

[RiversJohn]

Feel free to ask for more details or rewording if anything is unclear

[roji]

When commit is called but the action fails, e.g. illegal transaction and throws an exception

Commit() will throw an exception at that point, and the transaction will be rolled back.

Commit is never called and the transaction simply goes out of scope

The transaction is automatically rolled back.

I've assumed that the transaction failing and being disposed results in some kind of implicit RollBackAsync behaviour

Yes.

Additionally the usages of RollbackAsync aren't particularly clear

You'll have to be more specific.