You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The readme example explaining how sub dbs "are just regular levelup instances" is a bit ambiguous, in that it also seems to suggest that the createReadStream method is scoped to the sub:
The example and nested db's are just regular levelup instances:
example.put('hello','world',function(){nested.put('hi','welt',function(){// will print {key:'hello', value:'world'}example.createReadStream().on('data',console.log)})})
Except this doesn't appear to be the case. The above example actually prints:
Aye, sub.createReadStream() yields the entries of itself and any nested sublevels (because they are part of sub). Similar to how db.createReadStream() yields all entries.
Just my two cents but feels like this is the only feature that feels a bit cumbersome (but easy to work around!). Either way, IMO its worth updating the readme so the example shows the correct output, if only to save rookies like myself scratching a hole in their head. Happy to make a PR if that helps.
Either way, IMO its worth updating the readme so the example shows the correct output, if only to save rookies like myself scratching a hole in their head.
The readme example explaining how sub dbs "are just regular levelup instances" is a bit ambiguous, in that it also seems to suggest that the
createReadStream
method is scoped to the sub:Except this doesn't appear to be the case. The above example actually prints:
Is this intentional?
The text was updated successfully, but these errors were encountered: