Question: What differs the TpFIBDataSet.ApplyUpdToBase method from TpFIBDataSet.ApplyUpdates?

Answer: Both methods write changes made in the dataset to the database (if the CachedUpates dataset property is set to True). These methods show different behaviour when working with the local dataset cache.

Sending record changes to the database ApplyUpdates marks the records as processed. When changes of first N records have been successfully applied and N+1 changes were not applied, the transaction cannot be rolled back (as first N records are marked as processed, recurrent ApplyUpdates calls won’t be applied to their changes).

Unlike ApplyUpdates, ApplyUpdToBase does not do any operations with the local cache. This method only sends changes to the server. If you need to mark records as processed, you can use an additional CommitUpdToCache method.

So a successful execution of ApplyUpdates is similar to the consequence of two methods:

ApplyUpdToBase;
CommitUpdToCach;

If you use these two methods, you can handle errors more correctly. E.g.

with TpFIBDataSet1 do
   try
     ApplyUpdToBase;
     UpdateTransaction.Commit;
     CommitUpdToCach; 
      except
      UpdateTransaction.RollBack;
      raise
 end;

If no errors occur after this code is executed, the changes will be successfully applied to the database, committed by Commit and the local dataset cache will be marked as applied. In case any errors occur after the execution of ApplyUpdToBase, all the applied changes will be rolled back (UpdateTransaction.RollBack), and the dataset will be prepared for a new execution.




Preview text: 
Prices in Euro:

235 (1 copy)
1250 (unlimited)

Volume discounts are available...

Navigation



Devrace seems to have gone to great lengths to make a very high-quality, high-performance product! >>

Loren Szendre
FOR CUSTOMERS
Download full versions and updates in your Personal Area