Databases Reference
In-Depth Information
Aug10
UPDATE Policy [P861, , PPO, ]
J
Jan10
1
1
May10
2
1
3
4
3
2
1
Aug10
5
Jan
2010
Jan
2011
Jan
2012
Jan
2013
Jan
2014
eff-beg
asr-beg
epis-
beg
type
copay
row-crt
Row
#
1
oid
eff-end
asr-end
client
P861
Jan10
9999
Jan10
May10
Jan10
C882
C882
C882
C882
C882
HMO
Jan10
$15
May10
2
3
4
5
P861
P861
P861
P861
Jan10
May10
May10
9999
Jan10
Jan10
Jan10
Jan10
HMO
HMO
HMO
PPO
$15
$20
$20
$20
May10
May10
9999
Aug10
May10
Aug10
Aug10
9999
9999
Aug10
Aug10
May10
Aug10
9999
Aug10
Figure 7.13 Basic Scenario, Second Temporal Update: After the Third Physical Transaction.
contains the changes specified in the temporal update. The
result of doing this is shown in
Figure 7.13
. The transaction is
complete, and all locks have been released.
A Temporal Delete Transaction
Figure 7.13
shows us an asserted version table after a tempo-
ral insert and two temporal updates. This time, we will process a
temporal delete. As
Figure 7.14
shows, a temporal delete is trans-
lated into a set of physical update transactions which withdraw
the affected versions, followed by either one or two physical
insert transactions which delimit the scope of the delete and, if
necessary, any number of withdrawals and replacements to
adjust episode begin dates that may have been affected.
Temporal Delete
Physical Transaction(s)
Remove an object
from a designated
timespan.
Withdraw the affected versions.
Assert the replacements which
delimit the deletion.
Reset affected versions.
Figure 7.14 Basic Scenario, Delete Transaction: Temporal to Physical Mapping.
