Content deleted Content added
→Serializable: added superscripts to make it more clear |
m →View equivalence: Fixed formatting |
||
Line 242:
Additionally, two view-equivalent schedules must involve the same set of transactions such that each transaction has the same actions in the same order.
In the example below, the schedules S1 and S2 are view-equivalent, but neither S1 nor S2 are view-equivalent to the schedule S3.
{| class="wikitable"
! colspan="2" |S1
!S1: T1▼
! colspan="2" |S2
!S1: T2▼
! colspan="2" |S3
!S2: T1▼
|-
!S2: T2▼
!
!
|-
|R(A)
Line 265 ⟶ 269:
|
|-
|R(B)<sup>'''(1)'''</sup>
|
|
Line 281 ⟶ 285:
|Com.
|
|R(B)<sup>'''(1)'''</sup>
|
|
|R(B)<sup>'''(1)'''</sup>
|-
|
Line 297 ⟶ 301:
|Com.
|
|R(B)<sup>'''(2)'''</sup>
|
|-
|
|R(B)<sup>'''(2)'''</sup>
|
|R(B)<sup>'''(2)'''</sup>
|W(B)<sup>'''(3)'''</sup>
|
|-
|
|W(B)<sup>'''(3)'''</sup>
|
|W(B)<sup>'''(3)'''</sup>
|Com.
|
| |||