✨ [FEATURE] UnitOfWork --> EfCore Transactions and Rollbacks? about easyrepository.efcore HOT 3 CLOSED

UnitOfWork works with all or nothing logic.

Managing transactions is one method. However, no update or add method will be committed to the database without savechange running.
Users have to call UnitOfWork.Repository.Complete method because savechanges will not work without the Complete method in scope.

Supports EF Core Change Tracker feature. Tries to apply all changes to the context. If he gets an error on any of them, he can't perform any action anyway.

from easyrepository.efcore.

I respect that this is closed, and your explanation makes sense.

I am curious as to why Microsoft has a TransactionScope and a Rollback ability in this case?

I think this is more of an EfCore question, if you have time can you help me understand why this is the case?

For Example:

https://stackoverflow.com/questions/53324601/transaction-scope-for-different-repository-classes

public PizzaService(IDbContextScopeFactory contextScopeFactory, IPizzaRepo pizzaRepo, IPizzaIngredientsRepo ingredientRepo)
{
  _contextScopeFactory = contextScopeFactory;
  _pizzaRepo = pizzaRepo;
  _ingredientRepo = ingredientRepo;
}

public async Task SavePizza(PizzaViewModel pizza)
{
  using (var contextScope = _contextScopeFactory.Create())
  {
    int pizzaRows = await _pizzaRepo.AddEntityAsync(pizza.Pizza);
    int ingredientRows = await _ingredientRepo.PutIngredientsOnPizza(
      pizza.Pizza.PizzaId,
      pizza.Ingredients.Select(x => x.IngredientId).ToArray());

    contextScope.SaveChanges();
  }
}  

What is the advantage of the TransactionScope if its truly an 'all or nothing' logic?

from easyrepository.efcore.

This resource will be useful to you. @jeffward01

https://stackoverflow.com/questions/50844828/ef-db-savechanges-vs-dbtransaction-commit

from easyrepository.efcore.