Replace old memdb with level-mem

[vweevers]

This gives you:

• Continued compatibility with subleveldown. That it still worked on memdb was luck.
• Continued maintenance
• Latest streams (readable-stream)
• New features: db.clear(), db.iterator(), promise support, iterator.seek()
• Various fixes in the handling of binary keys (though y'all are not using that atm)
• Latest memdown internally stores data as buffers, which makes it fully compatible with leveldown (mixing strings and buffers is OK now). There could be a perf boost here because values can skip a Buffer.from(string) step but that's negated by a new conversion cost on keys (buf.toString()).
• I also added a buffer: true property to the custom JSON encoding used here. Not really needed because it defaults to true in most places, but it signals to underlying stores that data should be fetched as a buffer rather than a string, which avoids a conversion cost.

Caveats:

• Minimum node version is 6.
• null and undefined keys and values are rejected
• Conversely, null and undefined range options are now valid ({ gt: null } is not the same as {}).

[hackergrrl]

thank you vincent!

…

On 09/15 00:34, Vincent Weevers wrote: This gives you: - Continued compatibility with `subleveldown`. That it still worked on `memdb` was luck. - Continued maintenance - Latest streams (`readable-stream`) - New features: `db.clear()`, `db.iterator()`, promise support, `iterator.seek()` - Various fixes in the handling of binary keys (though y'all are not using that atm) - Latest `memdown` internally stores data as buffers, which makes it fully compatible with `leveldown` (mixing strings and buffers is OK now). There could be a perf boost here because values can skip a `Buffer.from(string)` step but that's negated by a new conversion cost on keys (`buf.toString()`). - I also added a `buffer: true` property to the custom JSON encoding used here. Not really needed because it defaults to `true` in most places, but it signals to underlying stores that data should be fetched as a buffer rather than a string, which avoids a conversion cost. Caveats: - Minimum node version is 6. - `null` and `undefined` keys and values are rejected - Conversely, `null` and `undefined` range options are now valid (`{ gt: null }` is not the same as `{}`). You can view, comment on, or merge this pull request online at: #57 -- Commit Summary -- * Replace old memdb with level-mem -- File Changes -- M index.js (7) M package.json (2) -- Patch Links -- https://github.com/cabal-club/cabal-core/pull/57.patch https://github.com/cabal-club/cabal-core/pull/57.diff -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: #57