01:19:12
| * Axy | joined |
01:19:12
| * Axy | quit (Changing host) |
01:19:12
| * Axy | joined |
01:22:28
| * Mia | quit (Ping timeout: 240 seconds) |
01:59:15
| * ekristen | quit (Quit: ekristen) |
07:38:12
| * Mia | joined |
07:40:49
| * Axy | quit (Ping timeout: 248 seconds) |
10:14:44
| * Axy | joined |
10:17:08
| * Mia | quit (Ping timeout: 240 seconds) |
12:48:01
| * Axy | quit (Ping timeout: 248 seconds) |
13:16:32
| * Mia | joined |
13:16:33
| * Mia | quit (Changing host) |
13:16:33
| * Mia | joined |
13:24:11
| * Mia | quit (Ping timeout: 240 seconds) |
13:39:11
| * Mia | joined |
13:39:11
| * Mia | quit (Changing host) |
13:39:11
| * Mia | joined |
15:22:09
| * Mia | quit (Ping timeout: 248 seconds) |
15:24:06
| * Mia | joined |
15:24:07
| * Mia | quit (Changing host) |
15:24:07
| * Mia | joined |
15:28:41
| * Mia | quit (Ping timeout: 240 seconds) |
15:29:38
| * Mia | joined |
15:29:38
| * Mia | quit (Changing host) |
15:29:38
| * Mia | joined |
19:27:43
| * aam | joined |
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
| * aam | part ("WeeChat 1.4") |