Separate sections of levelup, with hooks!
This module allows you to create seperate sections of a levelup database, kinda like tables in an sql database, but evented, and ranged, for real-time changing data.
The long awaited
level-sublevel rewrite is out!
You are hearby warned this is a significant breaking change.
So it's good to use it with a new project,
The user api is mostly the same as before,
but the way that keys are encoded has changed, and this means
you cannot run 6 on a database you created with 5.
Using leveldb with legacy mode is the simplest way to get the new sublevel on top of a database that used old sublevel. Simply require sublevel like this:
var level =// V *** require legacy.js ***var sublevel =var db =
@calvinmetcalf has created a migration tool: sublevel-migrate
This can be used to copy an old level-sublevel into the new format.
Unstable: Expect patches and features, possible api changes.
This module is working well, but may change in the future as its use is further explored.
var LevelUp =var Sublevel =var db =var sub = db//put a key into the main levelupdb//put a key into the sub-section!sub
Sublevel prefixes each subsection so that it will not collide with the outer db when saving or reading!
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 inserted with the triggering change.
Whenever a record is inserted, save an index to it by the time it was inserted.
var sub = dbdbdb
Notice that the
prefix property to
add() is set to
sub, which tells the hook to save the new record in the
sublevel batches also support a
prefix: subdb property,
if set, this row will be inserted into that database section,
instead of the current section, similar to the
pre hook above.
var sub1 = dbvar sub2 = dbsub