Multiversion Timestamp-based concurrency control -
in timestamp based concurrency command why have reject write in transaction t_i on element x_k if transaction t_j j > read it.
as stated in document.
if t_j not planing update @ why necessary restrictive on t_i's actions ?
optimistic-concurrency database-concurrency
No comments:
Post a Comment