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

add support for DeleteAllKeys update operation #49

Closed
cmumford opened this issue Sep 9, 2014 · 3 comments
Closed

add support for DeleteAllKeys update operation #49

cmumford opened this issue Sep 9, 2014 · 3 comments
Assignees

Comments

@cmumford
Copy link
Contributor

cmumford commented Sep 9, 2014

Original issue 43 created by josephwnorton on 2011-10-01T05:55:50.000Z:

It would be handy to have a new update operation that can delete all keys atomically without having to close, to delete, and then to re-open the database.

@cmumford
Copy link
Contributor Author

cmumford commented Sep 9, 2014

Comment #1 originally posted by sawloo on 2012-09-04T22:21:48.000Z:

something like Delete(start, limit) or Delete(range) will be great for me

@cmumford cmumford self-assigned this Sep 9, 2014
@cmumford
Copy link
Contributor Author

cmumford commented Sep 9, 2014

Comment #2 originally posted by sanjay@google.com on 2012-09-18T16:43:09.000Z:

I think we will not add this operation to leveldb since a helper routine
that accomplishes the same thing with equivalent performance can be
built outside leveldb.

@cmumford cmumford closed this as completed Sep 9, 2014
@genki
Copy link

genki commented Feb 23, 2017

@cmumford You mean deleting by iteration on a range is equivalent to Delete(range)?
Or there is something other way to accomplish it?
I think Delete(range) can be more efficient as it can perform compaction at same time.

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