00:07:29  * bthesorcerorquit (Quit: bthesorceror)
01:15:42  * bthesorcerorjoined
03:34:32  * bthesorcerorquit (Quit: bthesorceror)
03:59:36  * bthesorcerorjoined
04:15:15  * bthesorcerorquit (Quit: bthesorceror)
09:24:42  * binocarlosjoined
11:57:54  * bonswouarjoined
15:17:51  * jerrysvjoined
15:39:08  * bthesorcerorjoined
15:39:28  * bthesorcerorquit (Read error: Connection reset by peer)
15:40:27  * bthesorcerorjoined
15:41:00  * bthesorcerorquit (Read error: Connection reset by peer)
15:41:47  * bthesorcerorjoined
15:41:52  * bonswouarquit (Remote host closed the connection)
15:42:25  * bthesorcerorquit (Read error: Connection reset by peer)
15:43:22  * bthesorcerorjoined
15:43:38  * bthesorcerorquit (Read error: Connection reset by peer)
15:44:34  * bthesorcerorjoined
15:44:49  * bthesorcerorquit (Read error: Connection reset by peer)
15:45:34  * bthesorcerorjoined
15:45:46  * bthesorcerorquit (Read error: Connection reset by peer)
15:46:34  * bthesorcerorjoined
15:47:00  * bthesorcerorquit (Read error: Connection reset by peer)
15:47:48  * bthesorcerorjoined
15:49:38  * bthesorcerorquit (Read error: Connection reset by peer)
15:49:46  * bthesorcerorjoined
16:00:26  <ralphtheninja>tixz: you can use other encodings, e.g. bytewise https://github.com/deanlandolt/bytewise
16:11:15  <tixz>ralphtheninja: I looked at bytewise, but can I choose the order of keys? I have a key structure where I can exploit the keys for partitioning/indexing the dataset, but it requires the keys to be in a specific order
16:13:08  <tixz>ralphtheninja: All the uses cases sound wonderful (https://github.com/deanlandolt/bytewise#use-cases) but I guess I lack imagination :p
16:23:42  * jerrysvquit (Quit: Leaving...)
16:28:10  * sethvincentjoined
16:39:06  * jerrysvjoined
16:45:19  <ralphtheninja>tixz: post an issue on bytewise repo and ask dean :)
16:46:01  <ralphtheninja>be prepared for an extensive answer to your specific use case :)
17:07:09  <tixz>ralphtheninja: Haha, thanks will try :)
17:35:53  * jerrysv_joined
17:38:05  * jerrysvquit (Ping timeout: 244 seconds)
17:41:41  * jerrysv_changed nick to jerrysv
18:00:30  * bthesorcerorquit (Quit: bthesorceror)
18:01:24  * sethvincentquit (Ping timeout: 264 seconds)
18:14:13  * jerrysv_joined
18:15:09  * jerrysv__joined
18:15:11  * jerrysvquit (Read error: Connection reset by peer)
18:15:24  * jerrysv__changed nick to jerrysv
18:18:51  * jerrysv_quit (Ping timeout: 240 seconds)
19:13:12  * fiatjafjoined
19:13:40  <fiatjaf>is leveldb append-only?
19:26:03  * sethvincentjoined
19:36:20  * binocarlosquit (Ping timeout: 252 seconds)
21:07:46  * sethvincentquit (Ping timeout: 255 seconds)
21:42:51  <ogd>fiatjaf: it uses a technique called log structured merge trees which is based on append only logs
22:39:35  * jerrysvquit (Remote host closed the connection)
23:44:48  <fiatjaf>ogd: but we don't get access to past revisions, like couchdb?
23:45:17  <fiatjaf>also, the database tends to grow and grow forever, and it is impossible to reduce its size?