Matches in DBpedia 2014 for { <http://dbpedia.org/resource/Write–read_conflict> ?p ?o. }
Showing items 1 to 13 of
13
with 100 items per page.
- Write–read_conflict abstract "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 ST2 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.".
- Write–read_conflict wikiPageID "217741".
- Write–read_conflict wikiPageRevisionID "543696786".
- Write–read_conflict subject Category:Data_management.
- Write–read_conflict subject Category:Transaction_processing.
- Write–read_conflict comment "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 ST2 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.".
- Write–read_conflict label "Schreib-Lese-Konflikt".
- Write–read_conflict label "Write–read conflict".
- Write–read_conflict sameAs Write%E2%80%93read_conflict.
- Write–read_conflict sameAs Schreib-Lese-Konflikt.
- Write–read_conflict sameAs Q1493853.
- Write–read_conflict sameAs Q1493853.
- Write–read_conflict wasDerivedFrom Write–read_conflict?oldid=543696786.