EF 数据库事务可以循环使用吗？

Question

我有一个过程，我定期从数据库中检索记录，并对每个记录运行 3 个操作。对于每条记录，3 个操作必须要么全部成功，要么根本不成功。如果其中一个操作失败，我希望已经为之前的记录处理过的操作 已提交，因此下次进程运行时，它会获取之前 3 个事务之一失败的记录。

我想过将这 3 个操作包装在每条记录的事务中，并为每条记录循环，但我想确保在这种情况下使用数据库事务是有效的。以下是心中所想。对吗？

    public async Task OrderCollectionProcessorWorker()
    {
        using (var context = new DbContext())
        {
            try
            {
                IList<Order> ordersToCollect =
                    await context.Orders.Where(
                        x => x.OrderStatusId == OrderStatusCodes.DeliveredId)
                              .ToListAsync(_cancellationTokenSource.Token);

                await ProcessCollectionsAsync(context, ordersToCollect);
            }
            catch (Exception ex)
            {
                Log.Error("Exception in OrderCollectionProcessorWorker", ex);
            }
        }
    }


    /// <summary>
    /// For each order to collect, perform 3 operations
    /// </summary>
    /// <param name="context">db context</param>
    /// <param name="ordersToCollect">List of Orders for collection</param>
    private async Task ProcessCollectionsAsync(DbContext context, IList<Order> ordersToCollect)
    {
        if (ordersToCollect.Count == 0) return;

        Log.Debug($"ProcessCollections: processing {ordersToCollect.Count} orders");

        foreach (var order in ordersToCollect)
        {
            // group the 3 operations in one transaction for each order
            // so that if one operation fails, the operations performend on the previous orders
            // are committed
            using (var transaction = context.Database.BeginTransaction())
            {
                try
                {
                    // *************************
                    // run the 3 operations here
                    // operations consist of updating the order itself, and other database updates
                    Operation1(order);
                    Operation2(order);
                    Operation3(order);

                    // *************************

                    await context.SaveChangesAsync();

                    transaction.Commit();
                }
                catch (Exception ex)
                {
                    transaction?.Rollback();                        
                    Log.Error("General exception when executing ProcessCollectionsAsync on Order " + order.Id, ex);
                    throw new Exception("ProcessCollections failed on Order " + order.Id, ex); 
                }
            }
        }
    }

Answer 1

这似乎是一种正确的做法，除了在 catch 中您应该重新抛出异常或做其他事情以停止循环继续进行（如果我正确理解您的要求）之外。甚至没有必要使用

var transaction = context.Database.BeginTransaction()

因为

await context.SaveChangesAsync();

创建自己的事务。您所做的每项更改都存储在上下文中，当您调用 SaveChanges 时，会进行事务处理，并且所有更改都作为 1 批写入。如果发生故障，所有更改都将回滚。对 SaveChanges 的另一个调用将对新的更改进行另一个事务。但是请记住，如果事务失败，您不应再使用相同的上下文，而是创建一个新的上下文。总而言之，我会将您的方法编写如下：

private async Task ProcessCollectionsAsync(DbContext context, IList<Order> ordersToCollect)
{
    if (ordersToCollect.Count == 0) return;

    Log.Debug($"ProcessCollections: processing {ordersToCollect.Count} orders");

    foreach (var order in ordersToCollect)
    {
        // group the 3 operations in one transaction for each order
        // so that if one operation fails, the operations performend on the previous orders
        // are committed
        try
        {
            // *************************
            // run the 3 operations here
            // operations consist of updating the order itself, and other database updates
            Operation1(order);
            Operation2(order);
            Operation3(order);

            // *************************

            await context.SaveChangesAsync();
        }
        catch (Exception ex)
        {                     
            Log.Error("General exception when executing ProcessCollectionsAsync on Order " + order.Id, ex);
            throw;
        }
    }