What is level-sublevel?
The level-sublevel package is a plugin for LevelDB that allows you to create sublevel sections within a LevelDB database. This can help in organizing and managing data more effectively by creating isolated namespaces within the same database.
What are level-sublevel's main functionalities?
Creating Sublevels
This feature allows you to create sublevels within your LevelDB database. In the example, two sublevels 'users' and 'posts' are created, and data is added to each sublevel.
const level = require('level');
const sublevel = require('level-sublevel');
const db = level('./mydb');
const sub = sublevel(db);
const users = sub.sublevel('users');
const posts = sub.sublevel('posts');
users.put('user1', { name: 'Alice' }, function (err) {
if (err) return console.log('Ooops!', err);
console.log('User added!');
});
posts.put('post1', { title: 'Hello World' }, function (err) {
if (err) return console.log('Ooops!', err);
console.log('Post added!');
});
Batch Operations
This feature allows you to perform batch operations on a sublevel. In the example, multiple user records are added in a single batch operation.
const level = require('level');
const sublevel = require('level-sublevel');
const db = level('./mydb');
const sub = sublevel(db);
const users = sub.sublevel('users');
users.batch()
.put('user2', { name: 'Bob' })
.put('user3', { name: 'Charlie' })
.write(function (err) {
if (err) return console.log('Ooops!', err);
console.log('Batch operation complete!');
});
Stream Operations
This feature allows you to create a read stream to iterate over all entries in a sublevel. In the example, all user records are read and printed to the console.
const level = require('level');
const sublevel = require('level-sublevel');
const db = level('./mydb');
const sub = sublevel(db);
const users = sub.sublevel('users');
users.createReadStream()
.on('data', function (data) {
console.log(data.key, '=', data.value);
})
.on('error', function (err) {
console.log('Error:', err);
})
.on('end', function () {
console.log('Stream ended');
});
Other packages similar to level-sublevel
levelup
LevelUP is a higher-level module for working with LevelDB. It provides a more user-friendly API compared to the lower-level LevelDB bindings. While it does not provide sublevel functionality out of the box, it can be extended with plugins like level-sublevel.
subleveldown
Subleveldown is another package that provides sublevel functionality for LevelDB. It is similar to level-sublevel but is designed to work with the latest versions of LevelUP and LevelDB. It offers a more modern and maintained approach to creating sublevels.
level-party
Level-party is a package that allows multiple processes to safely share a single LevelDB instance. While it does not provide sublevel functionality directly, it can be used in conjunction with subleveldown or level-sublevel to achieve similar results.
level-sublevel
Separate sections of levelup, with hooks!
Status - Experimental
Anticipate Breaking Changes - please provide feedback.
Example
var LevelUp = require('levelup')
var Sublevel = require('level-sublevel')
var db = Sublevel(LevelUp('/tmp/sublevel-example'))
var sub = db.sublevel('stuff')
db.put(key, value, function () {
})
sub.put(key2, value, function () {
})
Sublevel prefixes each subsection so that it will not collide
with the outer db when saving or reading!
Hooks
Hooks are specially built into Sublevel so that you can
do all sorts of clever stuff, like generating views or
logs when records are inserted!
Records added via hooks will be atomically with the triggering change.
Hooks Example
Whenever a record is inserted,
save an index to it by the time it was inserted.
var sub = db.namespace('SEQ')
db.pre(function (ch, add) {
add({
key: ''+Date.now(),
value: ch.key,
type: 'put'
}, sub)
})
db.put('key', 'VALUE', function (err) {
sub.createReadStream()
.on('data', console.log)
})
Notice that sub
is the second argument to add
,
which tells the hook to save the new record in the sub
section.
Known Issues
Until this issue is closed https://github.com/rvagg/node-levelup/issues/86
hooks do not work correctly until the database is fully opened.
Use levelup(dir, function (err, db) {...})
to open db,
not var db = levelup(dir)
.
License
MIT