iterator: fix start after db end handling

Level / memdown

In-memory abstract-leveldown store for Node.js and browsers.

MIT License

287 stars 37 forks source link

Closed juliangruber closed 11 years ago

juliangruber commented 11 years ago

Without this fix a iterator that starts after the db end and isn't reversed will emit everything instead of nothing.

rvagg commented 11 years ago

ok, I'll believe you on this one

juliangruber commented 11 years ago

Before this fix, what happened was:

you create an iterator with start after the last key stored in the db
in https://github.com/rvagg/node-memdown/blob/master/memdown.js#L20-26 you tried to find the start position for iterating. but, in this case, none could be found
https://github.com/rvagg/node-memdown/blob/master/memdown.js#L30-31 then reset the start position to 0
therefore the iterate emitted all the data, instead of none of it