01:19:12  * Axyjoined
01:19:12  * Axyquit (Changing host)
01:19:12  * Axyjoined
01:22:28  * Miaquit (Ping timeout: 240 seconds)
01:59:15  * ekristenquit (Quit: ekristen)
07:38:12  * Miajoined
07:40:49  * Axyquit (Ping timeout: 248 seconds)
10:14:44  * Axyjoined
10:17:08  * Miaquit (Ping timeout: 240 seconds)
12:48:01  * Axyquit (Ping timeout: 248 seconds)
13:16:32  * Miajoined
13:16:33  * Miaquit (Changing host)
13:16:33  * Miajoined
13:24:11  * Miaquit (Ping timeout: 240 seconds)
13:39:11  * Miajoined
13:39:11  * Miaquit (Changing host)
13:39:11  * Miajoined
15:22:09  * Miaquit (Ping timeout: 248 seconds)
15:24:06  * Miajoined
15:24:07  * Miaquit (Changing host)
15:24:07  * Miajoined
15:28:41  * Miaquit (Ping timeout: 240 seconds)
15:29:38  * Miajoined
15:29:38  * Miaquit (Changing host)
15:29:38  * Miajoined
19:27:43  * aamjoined
19:28:03  <aam>hello -- what are some simple examples of use cases for leveldb?
19:28:21  <aam>aka, what would need large local caching in an application
21:09:52  <substack>aam: persisting data to disk, having more data than you can fit comfortably in memory
21:13:04  <substack>the kinds of things you might use another database for, but leveldb is more flexible as a lower-level component 
21:13:34  <substack>and leveldb in node has a very modular ecosystem of abstractions which is somewhat unique for a database
21:59:23  <aam>substack: cool, thank you!
21:59:35  * aampart ("WeeChat 1.4")