Revision as of 18:17, 18 August 2024 edit Dexxor (talk \| contribs) Extended confirmed users 2,729 edits →Strict: give example ← Previous edit		Revision as of 21:41, 1 February 2025 edit undo Frap (talk \| contribs) Extended confirmed users, File movers, Pending changes reviewers, Rollbackers 35,595 edits →Serializability Class Relationships: MOS:HEAD Next edit →
Line 539: Any strict schedule is cascade-less, but not the converse. Strictness allows efficient recovery of databases from failure. == Serializability ~~Class~~class ~~Relationships~~relationships == The following expressions illustrate the hierarchical (containment) relationships between [[serializability]] and [[Serializability#Correctness - recoverability\|recoverability]] classes:

Database transaction schedule: Difference between revisions