Open peoro opened 8 years ago
After some more digging I found out that the latest level-queryengine
, 3.0.1, depends on subindex
version 2.0.0, which, in turn, depends on level-sublevel
5.2.0.
It looks like level-sublevel
5 has the issue I mentioned above, while 6 fixes it: the read stream ignores sublevels. Some scripts I found and some level-sublevel
GitHub issues seem to confirm my hypothesis.
I believe that the latest version of subindex
(depending on level-sublevel
6) doesn't have any issue, and the problem here is level-queryengine
, which should depend on the latest subindex
.
I wonder how level-queryengine
could ever work: all the mentioned projects depend on specific (well, caret-preceded...) versions of each other...
I tried to run the sample code:
in an empty directory (just after a
npm install level-queryengine jsonquery-engine levelup leveldown
), and it fails:I tried to debug a little, and it looks like
db.indexDb.createReadStream
returns keys containing thelevel-sublevel
metadata (e.g.ÿindexesÿa0707461677300707461673100706865790000
).I'm not really sure why this is happening. Am I doing anything wrong, or did anything broke?