Explain why executions are always strict even if read locks are released after the last operation of
a transaction but before its commitment. Give an improved statement of Rule 2 in Figure 16.16.
What will be an ideal response?
Strict executions require that read and write operations on a data item are delayed until all transactions that
previously wrote that data item have either committed or aborted. The holding of a write lock is sufficient to
protect future transactions from non-strictness because we are concerned only with previous write operations.
Rule 2: When the client indicates that the last operation has been done (by a request to commit or abort), release
read locks. Hold write locks until commit or abort is completed.
You might also like to view...
You can use various units of measurement in Flash, including inches, points, and centimeters.
Answer the following statement true (T) or false (F)
What is the advantage of using structured English to communicate with people in the organization?
What will be an ideal response?
A(n) ____________________ loop should be used when the iterations should continue until a condition becomes true.
Fill in the blank(s) with the appropriate word(s).
The OSI model's Presentation layer translates data from lower layers into a format usable by the ____________________ layer, and vice versa.
Fill in the blank(s) with the appropriate word(s).