Recoverable cascading lost update and strict

Question

Comments

Yes and i think it is not cascading rollback..i said it wrong before.. It is just recoverable..

---

@minipanda

 its only recoverable. other false

---

its one of the complex thing in dbms to look at . i think?

Answer 1

   In this problem :

   some of them confused : its recoverable or not;

But its recoverable  because inrecoverable schedule is defined that rollback of committed transaction.

in this case first rollback than commit....so no problem its recoverble

but here casecading problem occurs ( if one transaction is rollback other transcation is effect)

not casecadeless

not strict

hence only recoverable schedule other is false.

Comments

OKK I AM STILL WITH THE UNRECOVERABLE .

SUPPOSE WE FIND AFTER  COMMIT C2 THAT OUR DATA IS WRONG FROM 1ST ONE. THEN WE CANT ROLLBACK AS IT IS COMMITED. WE CAN ONLY ROLL BACK IF STARTING W(A) DATA IS WRONG ,WHAT IF WE FIND AFTER COMMIT C2 THAT DATA IS WRONG AS 1ST TRANSACTION IS NOT COMMITED YET.

CORRECT ME IF I AM WRONG