Skip to content

wrap calculation of actual content constraint with transaction

The step to calculate the actual content constraint (ACC) should be wrapped by a transaction, to allow both versions (Live & PIT), and any substesps, of the ACC to be created or rollback at the same time.

It should also include a mechanism to detect if the ACC is up to date (synchronized) with the latest data/referential metadata import/transfer. For example, if there is a service failure during import/transfer, before reaching the step of the creation of the ACC, the values of the ACC might not represent the data/referential metadata values stored in the database. In this case the ACC should indicate if a recalculation is needed. One idea is that at the end of the merge steps, a flag (isUpToDate) will be set to false, and at the end of the calculation of the ACC it will be set to true.

  • Wrap calculation of the actual content constraint with a transaction
  • Add information to the actual content constraint to know if it is synchronized with the data in the database.
Edited by Pedro Carranza