Strictness
Strict schedules also eliminate the chance of writing dirty data.
A schedule is strict if
- no tx can read values written by another uncommitted tx (ACR)
- no tx can write a data item written by another uncommitted tx
Strict schedules simplify the task of rolling back after aborts.
|
![[prev]](icon/prev.gif){kind=icon}
![[next]](icon/next.gif){kind=icon}