Raghuramkrishnan

Question

T1	T2	T3
W(Y) commit	R(X) R(Y) W(Z) commit	W(X) commit

is this schedule a strict schedule?

Comments

@srestha cascading schedule is if there s a dirty read. where is dirty read in this schedule?

Answer 1

Strict schedules

 --->  A schedule is strict if: " A value written by a transaction T is not read or overwritten by other transactions until T either aborts or commits.

in the question x is written by 3 and after that T3 commit so now anyone can read or write on x

now  Y is written by T1 and after that T1 commit so now anyone can read or write on Y   after this 

in the schedule 

 Y is read by T2 so this is not a problem because T1 already commited

so it is strict schedule

GOOD READ https://gateoverflow.in/17082/difference-between-strict-schedule-cascadeless-schedule

Comments

@Gurdeep Saini

"Y is read by T2 so this is not a problem because T1 already commited

so it is strict schedule"

I think this statement should be : 

Y is read by T2 , this is  a problem because T1  is commited

after T2

so it isn't strict schedule

Plz correct me if I am wrong

---

T1  is commited after T2

watch the given schedule ,T1 is already committed  .... means before T2

---

Got it, my mistake