Blind write: Difference between revisions
Jump to navigation
Jump to search
imported>OAbot m Open access bot: doi updated in citation with #oabot. |
imported>Citation bot Alter: title, template type. Add: bibcode, isbn, chapter-url, chapter, authors 1-1. Removed or converted URL. Removed parameters. Some additions/deletions were parameter name changes. | Use this bot. Report bugs. | Suggested by Headbomb | #UCB_toolbar |
||
| Line 1: | Line 1: | ||
{{Short description|Computing term}} | {{Short description|Computing term}} | ||
In [[computing]], a '''blind write''', also known as a '''write-only transaction''', occurs when a [[database transaction|transaction]] writes a value without reading it.<ref>{{Cite | In [[computing]], a '''blind write''', also known as a '''write-only transaction''', occurs when a [[database transaction|transaction]] writes a value without reading it.<ref>{{Cite book |last1=Agrawal |first1=D. |last2=Krishnaswamy |first2=V. |chapter=Using multiversion data for non-interfering execution of write-only transactions |date=1991 |title=Proceedings of the 1991 ACM SIGMOD international conference on Management of data - SIGMOD '91 |chapter-url=https://doi.org/10.1145/115790.115801 |location=New York, New York, USA |publisher=ACM Press |pages=98–107 |doi=10.1145/115790.115801|isbn=0-89791-425-2 }}</ref> In particular, a write w<sub>i</sub>(X) is said to be blind if it is not the last action of resource X and the following action on X is a write w<sub>j</sub>(X).{{Citation needed|date=June 2025}} | ||
Blind writes can cause anomalies if multiple different blind write transactions are executed at the same time.<ref>{{Cite journal | | Blind writes can cause anomalies if multiple different blind write transactions are executed at the same time.<ref>{{Cite journal |last1=Herman |first1=Nanna Suryana |last2=Anshar |first2=Khairul |last3=Andono |first3=Pulung Nurtantio |date=2022-04-01 |title=Blind Write Protocol Throughput |journal=Journal of Physics: Conference Series |volume=2224 |issue=1 |pages=012074 |doi=10.1088/1742-6596/2224/1/012074 |issn=1742-6588|doi-access=free |bibcode=2022JPhCS2224a2074H }}</ref> | ||
Any [[database transaction schedule#View-serializable|view serializable]] schedule that is not [[database transaction schedule#Conflict-serializable|conflict serializable]] must contain a blind write.<ref>{{Cite book | | Any [[database transaction schedule#View-serializable|view serializable]] schedule that is not [[database transaction schedule#Conflict-serializable|conflict serializable]] must contain a blind write.<ref>{{Cite book |last1=Silberschatz |first1=Abraham |title=Database System Concepts |last2=Korth |first2=Henry |last3=Sudarshan |first3=S |date=2019-02-19 |publisher=[[McGraw-Hill]] |isbn=9780078022159 |edition=7th |chapter=Module 17: Transactions |chapter-url=https://www.db-book.com/slides-dir/PDF-dir/ch17.pdf |chapter-format=}}</ref> | ||
==References== | ==References== | ||
Latest revision as of 04:54, 26 June 2025
Template:Short description In computing, a blind write, also known as a write-only transaction, occurs when a transaction writes a value without reading it.[1] In particular, a write wi(X) is said to be blind if it is not the last action of resource X and the following action on X is a write wj(X).Script error: No such module "Unsubst".
Blind writes can cause anomalies if multiple different blind write transactions are executed at the same time.[2]
Any view serializable schedule that is not conflict serializable must contain a blind write.[3]