The diﬀerent schedules of transactions might ignore the operations ﬁnalized by other transactions.
Reason: conﬂicts with Read/Write operations
Conﬂicts are caused by the isolation property of transactions.
The isolation property might cause an anomaly in the database.
Four possible combination of Read/Write operations:
Read/Read, (Reading does not alter the state of the database. Just reading is always safe!)