auto

notes/salt.md

@@ -24,11 +24,16 @@ Issues:
 - non-repeatable reads
 - phantom
 
+## Big Things
+- BASE transactions
+- salt isolation
+- clever names
+
 ## BASE transactions
   - **alkaline** subtransactions
     - no other transactions can see state of *uncommitted alkaline subtrans*
     - **committed** alk subtrans state viewable by other BASE or alkaline transactions
-    - *not visible* until entire BASE commit.
+    - *not visible* (to ACID?) until entire BASE commit.
   - **salt isolation** allows control of internal states visibility (among other BASE transactions)
   - each alkaline sub has associated *exception*
   - *BASE transactions look like ACID transactions to other ACID transactions*
@@ -43,11 +48,11 @@ Issues:
     that exists between the earlier and the later of these operations  must extend to the
     entire transaction"* (allows SALT to work w/ different isolation levels)
 
-*Isolation:* Let Q be the set of operation types {read, range-read, write} and let L and S
-be subsets of Q . Further, let o1 in txn1 and o2 in txn2, be two operations, respectively
-of type T1 ∈ L and T2 ∈ S , that access the same object in a conflicting
-(i.e. non read-read) manner. **If o1 completes before o2 starts, then txn1 must decide
-before o2 starts.**
+*Isolation:* Let Q be the set of operation types {*read*, *range-read*, *write*} and let L and S
+be subsets of Q . Further, let $o_1$ in $txn_1$ and $o_2$ in $txn_2$, be two operations, respectively
+of type $T_1$ ∈ L and $T_2$ ∈ S , that access the same object in a conflicting
+(i.e. non read-read) manner. **If $o_1$ completes before $o_2$ starts, then $txn_1$ must decide
+before $o_2$ starts.**
 
 Isolation property holds if at least one is ACID, or both are alkaline.