Since release 1.1.8 of lmdb-store the following code now causes an error when breaking out of a cursor when reading the results of a dbi, same error occurs for getRange & I suspect all iterators. Is there a more preferred way of exiting the cursor?
false
true
-999.6743
-100
-22.2
0
C:\Users\kyleb\WebstormProjects\lmdb-test\index.js:58
console.log(key);
^
TypeError: Iterator result undefined is not an object
at Object.<anonymous> (C:\Users\kyleb\WebstormProjects\lmdb-test\index.js:58:13)
at Module._compile (internal/modules/cjs/loader.js:1137:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1157:10)
at Module.load (internal/modules/cjs/loader.js:985:32)
at Function.Module._load (internal/modules/cjs/loader.js:878:14)
at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:71:12)
at internal/main/run_main_module.js:17:47
Hi,
Since release 1.1.8 of lmdb-store the following code now causes an error when breaking out of a cursor when reading the results of a dbi, same error occurs for getRange & I suspect all iterators. Is there a more preferred way of exiting the cursor?
on version 1.1.11 the error out put is: