2017-05-30 44 views
1

在我的C#程序中,我使用实体框架将本地SQL Server数据库与QuickBooks数据同步。从QuickBooks获取数据似乎没有任何问题。然而,我在进行实体的批量提交时遇到了一个绊脚石。实体框架 - 如何处理批量SaveChanges失败

目前我正在用可配置数量的实体构建DataContext,然后批量提交实体。到目前为止批次没有失败,但如果它确实如此呢?我想解决这个问题的方法是迭代批处理,并一次提交一个实体,然后记录导致提交失败的那个实体。

但是我没有看到用数据上下文做这件事的方法,因为它在使用SaveChanges()时似乎是全部或无关紧要的。是否有办法处理我想要完成的任务,还是应该以完全不同的方式处理故障?

这里是我目前拥有的代码,如果你想看看它:

int itemsCount = 0; 
int itemsSynced = 0; 
int itemsFailed = 0; 

ArrayList exceptions = new ArrayList(); 

int batchSliceCount = Properties.Settings.Default.SyncBatchSize; //Getting the max batch size from the settings 
int index = 1; //Index used for keeping track of current batch size on data context 
List<Customer> currentBatch = new List<Customer>(); // List to hold curent batch 

db = new DataContext(DatabaseHelper.GetLocalDatabaseConnectionString()); 

foreach (var customer in QBResponse.customers) 
{ 
    itemsCount++; 

    try 
    { 
     string debugMsg = "Saving Customer with the Following Details....." + Environment.NewLine; 
     debugMsg += "ListId: " + customer.CustomerListId + Environment.NewLine; 
     debugMsg += "FullName: " + customer.FullName + Environment.NewLine; 
     int progressPercentage = (itemsCount * 100)/opResponse.retCount; 
     UpdateStatus(Enums.LogLevel.Debug, debugMsg, progressPercentage); 

     var dbCustomer = db.Customers.FirstOrDefault(x => x.CustomerListId == customer.CustomerListId); 

     if (dbCustomer == null) 
     { 
      // customer.CopyPropertiesFrom(customer, db); 
      Customer newCustomer = new Customer(); 
      newCustomer.CopyCustomer(customer, db); 
      newCustomer.AddBy = Enums.OperationUser.SyncOps; 
      newCustomer.AddDateTime = DateTime.Now; 
      newCustomer.EditedBy = Enums.OperationUser.SyncOps; 
      newCustomer.EditedDateTime = DateTime.Now; 
      newCustomer.SyncStatus = true; 

      db.Customers.Add(newCustomer); 
      currentBatch.Add(newCustomer); 
     } 
     else 
     { 
      //dbCustomer.CopyPropertiesFrom(customer, db); 
      dbCustomer.CopyCustomer(customer, db); 
      dbCustomer.EditedBy = Enums.OperationUser.SyncOps; 
      dbCustomer.EditedDateTime = DateTime.Now; 
      dbCustomer.SyncStatus = true; 
      currentBatch.Add(dbCustomer); 
     } 

     try 
     { 
      if (index % batchSliceCount == 0 || index == opResponse.customers.Count()) //Time to submit the batch 
      { 
       UpdateStatus(Enums.LogLevel.Information, "Saving Batch of " + batchSliceCount + "Customers to Local Database"); 
       db.SaveChanges(); 
       itemsSynced += currentBatch.Count(); 
       currentBatch = new List<Customer>(); 
       db.Dispose(); 
       db = new DataContext(DatabaseHelper.GetLocalDatabaseConnectionString()); 
      } 
     } 
     catch (Exception ex) 
     { 
      string errorMsg = "Error occured submitting batch. Itterating and submitting one at a time. " + Environment.NewLine; 
      errorMsg += "Error Was: " + ex.GetBaseException().Message + Environment.NewLine + "Stack Trace: " + ex.GetBaseException().StackTrace; 
      UpdateStatus(Enums.LogLevel.Debug, errorMsg, progressPercentage); 

      //What to do here? Is there a way to properly iterate over the context and submit a change one at a time? 
     } 
    } 
    catch (Exception ex) 
    { 
     //Log exception and restart the data context 
     db.Dispose(); 
     db = new DataContext(DatabaseHelper.GetLocalDatabaseConnectionString()); 
    } 

    Thread.Sleep(Properties.Settings.Default.SynchronizationSleepTimer); 
    index++; 
} 
+0

确实难以解决的问题,这就是我会做的......如果SaveChanges出现异常,我会尝试将内容写入日志,以便至少所做的更改仍然可用。然而,EF应该照顾这项权利,因为它具有“跟踪”能力。我从来没有必须与恢复工作,所以我只是想在这里大声。 –

回答

0

这取决于你想从收回的例外......

如果您正在寻找一种方法来重试连接是否中断,您可以使用自定义执行策略基于DbExecutionStrategy,如果发生特定错误,如CodeProject文章中所述,则重试。

+0

我知道使用执行策略来处理超时。我还没有实施它,但它在发展路线图上。我更关心异常,例如关键违规(I.E.正在提交的实体批处理被SQL Server拒绝)。 – Stephen

+0

,因为没有办法重试可以解决密钥违规错误我建议您在尝试将其安全地存储到商店之前自行验证批处理 – user1859022