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

Discontinue RocksDB binding #141

Merged
merged 1 commit into from
Dec 1, 2024
Merged

Discontinue RocksDB binding #141

merged 1 commit into from
Dec 1, 2024

Conversation

vweevers
Copy link
Member

@vweevers vweevers commented Dec 1, 2024

Closes #121.

This is a heads up rather than a discussion. That's because rocksdb and level-rocksdb use the old abstract-leveldown and levelup packages (rather than abstract-level) so if anyone wants to pick it up, it would have to be a new npm package anyway which can start in user land. E.g. a rocks-level package which would be the equivalent of classic-level.

This was referenced Dec 1, 2024
@vweevers vweevers changed the title Discontinue rocksdb Discontinue RocksDB binding Dec 1, 2024
@vweevers vweevers merged commit d0f26ee into master Dec 1, 2024
2 checks passed
@vweevers vweevers deleted the no-rocks branch December 1, 2024 20:49
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

Successfully merging this pull request may close these issues.

rocks-level implementation
1 participant