07:16:17  * rvaggquit (Read error: Connection reset by peer)
07:16:27  * rvagg_joined
07:16:56  * jcrugzz_joined
07:17:14  * timwis_joined
07:18:46  * jcrugzzquit (Read error: Connection reset by peer)
07:18:46  * timwisquit (Ping timeout: 240 seconds)
07:18:49  * jcrugzz_changed nick to jcrugzz
07:19:14  * timwis_changed nick to timwis
12:27:50  * pcmindjoined
12:57:17  * pcmindquit (Quit: Page closed)
18:55:09  <Veejay>ralphtheninja: No worries, it's IRC, I am screened, I don't mind asynchronous
18:55:14  <Veejay>Thanks
18:57:38  <Veejay>When using leveldb in NodeJS through the various packages and retrieving data from the database using queries is it common practice to implement the filtering as a transform stream?
18:58:03  <Veejay>If so, is through2 the canonical package to achieve that, or is there something more leveldb-idiomatic?
18:58:27  <Veejay>I've found it to work very well but I might be reinveting the wheel
18:59:07  <Veejay>An example would be a bunch of users, and I want to get users where age is higher than some user-defined threshold
19:09:32  <ralphtheninja>that should work fine
19:09:38  <ralphtheninja>yeah through2 is commonly used
19:10:00  <ralphtheninja>also, there's a tonne of modules on npm for various level stuff
19:10:03  <ralphtheninja>search for level-
19:12:45  <ralphtheninja>Veejay: it's also common to use sub-levels and create keys for indexing
19:16:10  <ralphtheninja>so you could have a sub level, which contains elements that are keyed on `age-user_id` and you could do something like sub.createReadStream({ gt: '22-', lt: '33-~' }) which would stream all users from the age of 22 to 33
19:16:35  <ralphtheninja>maybe not ideal keys, but you get the idea
19:19:09  <ralphtheninja>but maybe indexing is not even required, say you have 100 users you don't care but if you have 10 million you don't want to stream the whole database through a filter
19:19:24  <ralphtheninja>trade offs :)
20:11:50  * laduke13quit (Ping timeout: 256 seconds)
20:12:15  * laduke13joined