02:26:54  * sethvincentquit (Ping timeout: 244 seconds)
04:02:36  * smariquit (Ping timeout: 264 seconds)
06:33:59  * ldbgooglejoined
06:34:50  <ldbgoogle>leveldb.org has an example page. here is some sample example https://github.com/kennetham/LevelDB-Playground
06:49:47  * ldbgooglequit (Quit: Page closed)
07:21:31  * bonswouarjoined
09:13:50  * binocarlosjoined
10:11:39  * smarijoined
10:16:26  * smariquit (Ping timeout: 246 seconds)
10:17:14  * smarijoined
10:22:03  * smariquit (Ping timeout: 268 seconds)
14:58:38  * jerrysvjoined
15:13:50  * mhernandez1joined
15:22:59  * bonswouarquit (Remote host closed the connection)
15:44:29  <daleharvey>hrm, what is the expected behaviour opening leveldb's in seperate processes
15:44:59  <daleharvey>I was hoping to have one background process doing reads / writes, and one that just read data
15:46:20  <daleharvey>as far as I can tell what happens now is once one process has a lock / open file, the other one is being locked out
15:47:13  <Aria>Correct, because some of the levels are in RAM
15:51:46  <daleharvey>ok, can figure out how to stuff them in the same process, cheers
16:48:45  * sethvincentjoined
16:55:20  * binocarlosquit (Ping timeout: 240 seconds)
17:18:52  * delaneyjoined
17:21:11  <delaney>Good morning, is it possible to do path traversal with level-sublevel?
17:22:09  <delaney>like const a = db.sublevel('a'); const b = db.sublevel('b'); b.sublevel('../a').doStuffOnA() ?
19:25:12  * mhernandez1quit (Remote host closed the connection)
19:48:09  * delaneyquit (Ping timeout: 268 seconds)
20:09:38  * binocarlosjoined
20:55:24  * paxos2kquit (Quit: ZNC - http://znc.in)
20:55:47  * binocarlosquit (Ping timeout: 265 seconds)
22:46:21  * jerrysvquit (Remote host closed the connection)
23:23:00  * sethvincentquit (Ping timeout: 264 seconds)
23:31:55  * timoxleyjoined
23:32:51  * timoxley_quit (Ping timeout: 246 seconds)