4 ms·
Could you expand a little on how you're doing that? I've been thinking about transitioning entirely to sqlite for all my data.
by limomium 7y ago
Could you expand a little on how you're doing that?
I've been thinking about transitioning entirely to sqlite for all my data.
- zippie 7y agoThe GP may seem like sarcasm to some ... sqlite is an overlooked, novel, and faster way (up to 35%!) to store things than the filesystem [0]. You can use something like libsqlfs [1] for POSIX file heuristics with sqlite as the backing store. One HA single primary/multi-master solution to use sqlite may be drbd. [0] https://www.sqlite.org/fasterthanfs.html https://www.sqlite.org/fasterthanfs.html [1] https://github.com/guardianproject/libsqlfs https://github.com/guardianproject/libsqlfs
- pdimitar 7y agoThere's no hard formula. It's basically forming a habit to never use file I/O and use SQL queries instead. Bonus points for the `lsm1` extension of sqlite3 which allows you to use it as a key-value store, which I used with mixed success (if I could remember the key names that seemed the most logical thing in the world last week, lol). There's nothing to it, really. sqlite3 is a very mature software and save for a mechanical failure of your storage drive, the odds of it losing your data are practically zero. For even more bonus points, encrypt your sqlite3 storage. That way you can freely distribute it on Git hosting services.