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
DoNotOverwrite - feature request #139
Comments
If I'm understanding correctly this can be easily fixed by application code to synchronize these two threads. This doesn't sound like a feature that should be in the database. |
Personally I think it would be convenient to have this as a WriteOption. The issue can be worked around in application code, but it can still be a bit of a pain / gotcha. IndexedDB appears to specify this functionality: so, in addition to being handy for Node peoples, having this feature here might even simplify Chromium's implementation? |
Upstream had refused to add pkg-config due to moved to cmake, so pick up Homebrew/legacy-homebrew#31773 again and fix google/leveldb#139
Fix doc sample typos in header and README
Original issue 133 created by doppelbauer on 2012-12-27T21:21:37.000Z:
It would be great to have a WriteOption "DoNotOverwrite".
If two threads append a new record (new_key = last_key + 1), they would overwrite their records.
The text was updated successfully, but these errors were encountered: