Proactive Updates, Part 2

In the “Time and Time Again: Scenario 1” installment, and continuing through Transaction 2, 3, and 4, we developed Scenario 1. This is the “plain vanilla” scenario for asserted versioning. It consists of an original insert, two original updates and an original delete. In our experience, 75 percent or more of the transactions against asserted version tables are covered by Scenario 1. This is because the Scenario 1 transactions accept default values for all three bi-temporal dates that may be specified on original transactions. These dates are, in the positional sequence in which they appear on those transactions – the effective begin date, effective end date and the assertion begin date. The default value for the begin dates is the date the transaction is applied. The default value for the effective end date is 12/31/9999.

via Proactive Updates, Part 2.