Timeline for Partial order, total order, and version order in transaction histories
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Jan 10, 2015 at 13:15 | history | suggested | hengxin | CC BY-SA 3.0 |
latex for symbols
|
| Jan 10, 2015 at 12:01 | review | Suggested edits | |||
| S Jan 10, 2015 at 13:15 | |||||
| Jan 10, 2015 at 8:22 | vote | accept | hengxin | ||
| Jan 10, 2015 at 8:02 | comment | added | hengxin | Great thanks! For the total version order, Adya also comments: "The version order in a history $H$ can be different from the order of write or commit events in $H$. This flexibility is needed to allow certain optimistic and multi-version implementations where $\ldots$" (Have been added to the question). Is this the thing of "allowing the implementation of a database to access a version of an object which precedes (in the version order) the latest version installed"? | |
| Jan 8, 2015 at 11:55 | review | First posts | |||
| Jan 8, 2015 at 12:39 | |||||
| Jan 8, 2015 at 11:48 | history | answered | Andrea Cerone | CC BY-SA 3.0 |