Skip to content
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

Transaction Support #118

Open
qpfiffer opened this issue Sep 10, 2014 · 4 comments
Open

Transaction Support #118

qpfiffer opened this issue Sep 10, 2014 · 4 comments
Assignees
Milestone

Comments

@qpfiffer
Copy link
Member

General ticket for transactions. API, implementation, ideas, thoughts, etc. Transactions should have the following goals:

  • Make all operations inside a transaction atomic
  • Lock the database to prevent unwanted bullshit
  • Easy-to-use
  • Durable, which means all writes in the transaction should be synced to disk, even before the transaction is committed.
@qpfiffer qpfiffer self-assigned this Sep 10, 2014
@qpfiffer qpfiffer added this to the 0.1.5 milestone Sep 10, 2014
@colby
Copy link
Contributor

colby commented Sep 10, 2014

💸 💸 💸

@kyleterry
Copy link
Member

Yup! 👍

@qpfiffer
Copy link
Member Author

Going to do multiple, I think. I'll hold all current committed transactions in a splay tree, and then all transaction commands will require a transaction ID for lookup.

@Hamcha
Copy link
Member

Hamcha commented Sep 11, 2014

👍 for multiple

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants