词条 | Write–read conflict |
释义 |
In computer science, in the field of databases, write–read conflict, also known as reading uncommitted data, is a computational anomaly associated with interleaved execution of transactions. Given a schedule S T2 could read a database object A, modified by T1 which hasn't committed. This is a dirty read. T1 may write some value into A which makes the database inconsistent. It is possible that interleaved execution can expose this inconsistency and lead to inconsistent final database state, violating ACID rules. Strict 2PL overcomes this inconsistency by locking T2 out from performing a Read/Write on A. Note however that Strict 2PL can have a number of drawbacks, such as the possibility of deadlocks. See also
References{{Unreferenced|date=August 2009}}{{DEFAULTSORT:Write-Read Conflict}} 2 : Data management|Transaction processing |
随便看 |
|
开放百科全书收录14589846条英语、德语、日语等多语种百科知识,基本涵盖了大多数领域的百科知识,是一部内容自由、开放的电子版国际百科全书。