-
-
Notifications
You must be signed in to change notification settings - Fork 13
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
QOL API methods #73
Comments
I'm +-0 on the first two, as discovering first and last key is cheap, and it's convenient indeed. However it's also simple and infrequently desired enough that it could live in userland. -1 to the third method, because it means a full table scan and in many scenarios where you need something like leveldb (have a lot of data) isn't actually what you want to do |
Agree with @juliangruber on the first two. Not sure I understand the third method. Can you give an example? |
I imagine it's something like https://github.com/juliangruber/level-exists/blob/master/index.js |
Let's assume that's the case (shouldn't require iteration though). That's covered by Level/community#106 so I'll close this. |
While we're contributing, we were wondering if you had any interest in any of the following quality of life methods we've added to our wrapper for ClassicLevel:
compactFull
- Convenience function that discovers the first and last key and callscompactRange
size
- Convenience function that discovers the first and last key and callsapproximateSize
has
- Definitely a feature that would be better if it existed upstream, but iterates keys until specified key is discovered (if at all)The text was updated successfully, but these errors were encountered: