I was checking if the reverse option was already implemented in ./lib/iterator, because I might need it for a project I'm working on. Turns out it is, so this patch adds this information to the API documentation for createReadStream.
I'm wondering though whether reading records in reverse order will affect performance, like it does in LevelDB. If thats the case I could add another line to the documentation to point that out.
I was checking if the
reverse
option was already implemented in./lib/iterator
, because I might need it for a project I'm working on. Turns out it is, so this patch adds this information to the API documentation forcreateReadStream
.I'm wondering though whether reading records in reverse order will affect performance, like it does in LevelDB. If thats the case I could add another line to the documentation to point that out.