science

Write–read conflict

Write–read conflict is a science topic covered in the lgStudy science library. This page brings together a partial reference excerpt, illustrations, worked examples, real-world applications and a short study plan, so you can understand Write–read conflict rather than just read about it. In short: In computer science, in the field of databases, write–read conflict (also known as reading uncommitted data and dirty read), is a computational anomaly associated with interleaved execution of transactions. Specifically, a write–read conflict occurs when "a transaction requests to write an entity, for which an unclosed transaction has already made a read request." Given a schedule S S = [ T 1 T 2 R ( A ) W ( A ) R (…

Key takeaways

Write–read conflict belongs to science; place it in that map before memorising details.
Learn the definition first, then one example that makes the definition concrete.
Connect Write–read conflict to a quantity you can measure, compute or draw — that is where exam questions come from.
Reproduce the core statement of Write–read conflict from memory before moving on to harder problems.

Reference excerpt

In computer science, in the field of databases, write–read conflict (also known as reading uncommitted data and dirty read), is a computational anomaly associated with interleaved execution of transactions. Specifically, a write–read conflict occurs when "a transaction requests to write an entity, for which an unclosed transaction has already made a read request." Given a schedule S

S = [ T 1 T 2 R ( A ) W ( A ) R ( A ) W ( A ) R ( B ) W ( B ) C o m . R ( B ) W ( B ) C o m . ] {\displaystyle S={\begin{bmatrix}T1&T2\\R(A)&\\W(A)&\\&R(A)\\&W(A)\\&R(B)\\&W(B)\\&Com.\\R(B)&\\W(B)&\\Com.&\end{bmatrix}}}

T2 could read a database object A, modified by T1 which hasn't committed. This is a dirty or inconsistent 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 an 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 Concurrency control Read–write conflict Write–write conflict

References

Worked examples

Example 1 — a first encounter with Write–read conflict

Start with the simplest possible case. Write down what Write–read conflict claims or describes in one sentence, then invent the smallest concrete situation in which that sentence is true. In science, the smallest case is usually a single object, a single equation or a single measurement. Check that every symbol or term in your sentence has a meaning in that case.

Example 2 — changing one variable

Take the situation from Example 1 and change exactly one quantity: double it, halve it, or set it to zero. Predict what should happen to Write–read conflict before you calculate. Comparing your prediction with the result is the fastest way to find out whether you understand the idea or only the words.

Example 3 — an exam-style question

Typical questions about Write–read conflict ask you to (a) state it precisely, (b) apply it to given data, and (c) explain a limitation. Practise writing all three answers in under five minutes; the third part is what separates a full-mark answer from an average one.

Applications of Write–read conflict

In research: Write–read conflict appears in science research whenever the underlying quantities have to be modelled precisely. Papers usually cite it as a starting assumption and then explore where it breaks down.
In technology and industry: Engineering practice reuses Write–read conflict in design rules, simulations and safety margins. Knowing the idea lets you read a specification sheet and understand why the numbers look the way they do.
In the classroom: Write–read conflict is common in secondary-school and first-year university syllabi. It links to neighbouring topics Data management, Transaction processing, so understanding it makes those chapters shorter.
In everyday life: Look for Write–read conflict outside the textbook — in sport, cooking, traffic, electronics or the sky above you. An example you found yourself is remembered far longer than one you were given.

Ask Teacher Smith questions about this articleOpens your AI tutor with a question about “Write–read conflict” →

Affiliate

Preply — study more efficiently by working with a personal tutor. 50% off.

How to study Write–read conflict in 20 minutes

Read the reference excerpt below once, without taking notes.
Close the page and write down what Write–read conflict means in your own words.
Compare your version with the excerpt and mark what you missed.
Work through the three examples above with pen and paper.
Explain Write–read conflict out loud to somebody else — or to Teacher Smith in the lgStudy chat.

Frequently asked questions

What is Write–read conflict in simple terms?

Why does Write–read conflict matter?

Because it connects several science ideas at once: it gives you a definition you can apply, a quantity you can calculate, and a way to check whether a result is plausible.

How should I study Write–read conflict?

Read the excerpt, restate it from memory, then work through the examples and applications listed on this page. The five-step study plan above takes about twenty minutes.

What does this page cover?

It gives you a compact reference excerpt plus original lgStudy explanations, examples, applications and study material on Write–read conflict.