Database transaction schedule: Difference between revisions

Content deleted Content added
Tag: Reverted
Undid revision 1236623893 by 217.197.97.50 to restore original meaning. The schedule is trivially recoverable since no transaction reads from another
Line 530:
|}
 
Note that this Schedule would not be recoverableserializable if T1 would be committed.
Cascading aborts avoidance is sufficient but not necessary for a schedule to be recoverable.