Revision as of 07:33, 16 July 2024 edit 666-Bandera Mouse (talk \| contribs) 221 edits No edit summary ← Previous edit		Revision as of 17:35, 25 July 2024 edit undo 217.197.97.50 (talk) No edit summary Next edit →
Line 452: These schedules are recoverable. The schedule F is recoverable because T1 commits before T2, that makes the value read by T2 correct. Then T2 can commit itself. In the F2 schedule, if T1 aborted, T2 has to abort because the value of A it read is incorrect. In both cases, the database is left in a consistent state. ~~Transaction~~Schedule J is unrecoverable because T2 committed before T1 despite previously reading the value written by T1. Because T1 aborted after T2 committed, the value read by T2 is wrong. Because a transaction cannot be rolled-back after it commits, the schedule is unrecoverable. ====Cascadeless====

Database transaction schedule: Difference between revisions