![]() ![]() ![]() ![]() ![]() Next: Conclusion Up: Consistency Previous: Operation Level Consistency   Contents   Index |
If the system guarantees that transactions are atomic, isolated, and durable then system level consistency is no more than operation level consistency--if transactions that produce correct result when executed alone, are executed as if they were alone, then they will produce correct results.
If, for instance, the system does not guarantee isolation, additional requirements4.3may be put on the transactions for the system to make any promises. In ORACLE transactions are not isolated and additional locking is required [37]:
"SELECT FOR UPDATE [that acquires explicit row locks] is recommended when you need to lock a row without actually changing it. For example, if you intend to base an update on the existing values in a row, you need to make sure the row is not changed by someone else before your update."
![]() ![]() ![]() ![]() ![]() Next: Conclusion Up: Consistency Previous: Operation Level Consistency   Contents   Index |