Skip to content

Conversation

@TurtleTony
Copy link

Specification and verification of possible anomalies that can occur in concurrent transactions.

… isolation

Signed-off-by: Tristan Schönhals <tristan.schoenhals@gmail.com>
@TurtleTony
Copy link
Author

I'm planning to post about this model in the discourse group. Thanks to @esb-dev for the inspiration and idea! :-)

@grayswandyr
Copy link

Looks interesting. I suggest we discuss this first on Discourse, before adding a definitive version in this repo.

@TurtleTony
Copy link
Author

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 <tristan.schoenhals@gmail.com>
The terminology was originally following the TLA+ example, but commit is the better terminology in this context

Signed-off-by: Tristan Schönhals <tristan.schoenhals@gmail.com>
@TurtleTony
Copy link
Author

Makes it a lot simpler to read :-)

Signed-off-by: Tristan Schönhals <tristan.schoenhals@gmail.com>
This clearly communicates whether assertions are meant to fail or succeed

Signed-off-by: Tristan Schönhals <tristan.schoenhals@gmail.com>
Signed-off-by: Tristan Schönhals <tristan.schoenhals@gmail.com>
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 <tristan.schoenhals@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants