Recovery and Atomicity Modifying the database without ensuring that the transaction will commit may leave the database in an inconsistent state. Consider transaction T;that transfers $50 from account A to account B; goal is either to perform all database modifications made by 7;or none at all. Several output operations may be required for T;(to output A and B).A failure may occur after one of these modifications have been made but before all of them are made. Database System Concepts,5th Edition,Oct 5,2006 17.11 ©Silberschat乜，Korth and SudarshanDatabase System Concepts, 5 17.11 ©Silberschatz, Korth and Sudarshan th Edition, Oct 5, 2006 Recovery and Atomicity Modifying the database without ensuring that the transaction will commit may leave the database in an inconsistent state. Consider transaction Ti that transfers $50 from account A to account B; goal is either to perform all database modifications made by Ti or none at all. Several output operations may be required for Ti (to output A and B). A failure may occur after one of these modifications have been made but before all of them are made