-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add a key-value-store with snapshot isolation #27
base: master
Are you sure you want to change the base?
Conversation
… isolation Signed-off-by: Tristan Schönhals <[email protected]>
I'm planning to post about this model in the discourse group. Thanks to @esb-dev for the inspiration and idea! :-) |
Looks interesting. I suggest we discuss this first on Discourse, before adding a definitive version in this repo. |
Sure, good suggestion! I'll make a post later and link it here. |
Fix typos, add references, correct the information regarding oracle's serializable, and re-write some unprecise sentences Signed-off-by: Tristan Schönhals <[email protected]>
The terminology was originally following the TLA+ example, but commit is the better terminology in this context Signed-off-by: Tristan Schönhals <[email protected]>
Follow the discussion here: |
Makes it a lot simpler to read :-) Signed-off-by: Tristan Schönhals <[email protected]>
This clearly communicates whether assertions are meant to fail or succeed Signed-off-by: Tristan Schönhals <[email protected]>
Signed-off-by: Tristan Schönhals <[email protected]>
It was quite redundant. OpenTransaction is now tracked through a var sig (makes a lot more sense) . The current state of the store is still represented through the store relation but it now lives inside the Key sig Signed-off-by: Tristan Schönhals <[email protected]>
Specification and verification of possible anomalies that can occur in concurrent transactions.