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

control over write volatility #25

Open
nponeccop opened this issue Aug 8, 2011 · 1 comment
Open

control over write volatility #25

nponeccop opened this issue Aug 8, 2011 · 1 comment

Comments

@nponeccop
Copy link
Contributor

I don't know the proper term for what I called write volatility, so let me explain.

If someone repeatedly calls db.set() with the same key, dirty has two options:

  1. to write every set() to disk
  2. to write only the last set() to disk

In certain situations both (1) and (2) can be useful, so I'd like to have an option when I open a database.

@felixge
Copy link
Owner

felixge commented Aug 8, 2011

Hi, the features you are suggesting sound good, but unfortunately I won't have time to work on any of them in the near future. Feel free to send me pull requests so.

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

No branches or pull requests

2 participants