Skip to content

Conversation

@mpardalos
Copy link
Contributor

I have an implementation of a lot of the transaction features in SQL, however I'm still missing some things that might be useful, most notably a notion of queries (every event is now considered as it's own "query") and serializable transactions.

I'm leaving this draft PR here as a place to make notes that might be of interest. I'm marking it as draft since I haven't found any interesting executions yet and I also like to add some things (like the weakening we talked about). If you think it should be merged in its current state I'd be happy to unmark it.

Ban them directly (i.e. ban reads reading different values for
apparently no reason) insteads of trying to prevent them indirectly
They were not used anyway (yet)
If a .als model imports a .cat model, convert it to als as necessary
Necessary because we need multiple formulations of serializability
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.

1 participant