Dirty read is where one transaction writes an attribute and then another transaction reads the changed attribute without the first transaction committing. This is not true in this case.
Dirty read, also known as the Uncommitted Dependency, is where one transaction writes an attribute and then another transaction reads the changed attribute without the first transaction committing. This is not true in this case.
The incomsistent analysis scenario depicts how certain interleaving of transactions can result in the wrong modifications to the database, as the interleaving is not serialisable. This is not true in this case.
In lost update, a modification is lost due to another transaction overwriting the modification.
Deadlock can only occur in a system with concurrency control. This is not the case here as the question clearly states that the system under consideration has no concurrency control.
In an DBMS without concurrency control, what consistency problem does the following transaction schedule depict?
| Time | Transaction A | Transaction B |
|---|---|---|
| t1 | read R | |
| t2 | read R | |
| t3 | write R | |
| t4 | write R |
- Dirty Read
- Uncommitted Dependency
- Inconsistent Analysis
- Lost Update
- Deadlock
| ||||
| ||||
|