Thanks for submitting. I was pleasantly surprised to see the author recommending a very simple database schema. I don’t like SQL, but I think I would be content to use it for the incremental update and random access benefits if the schema were simple.
It’s easy for the OpenDocument case to just say “use plain text files, images and git”, but I’m convinced that using sqlite or designing your own careful file format is a good solution for applications.
I’ve been using SQLite as the application format for various projects. It is easy to use because it is ubiquitous. I can package SQLite myself; I can use SQLite from the distro; I can update as I go; I don’t need to worry about saving took long time. As long as I stick with the basics, it works everywhere.
That has been said, it is interesting that in many places, I do find the application format end-up as a simple key-value pairs, or a web (tree?) of hierarchical objects. Both SQLite can model, however, both are not tabular per-se. Something like HDF5 seems model better for my hierarchical objects. However, packaging HDF5 with various wrappers is a challenge by itself, and SQLite has APIs I am already familiar / enjoying with.
Thanks for submitting. I was pleasantly surprised to see the author recommending a very simple database schema. I don’t like SQL, but I think I would be content to use it for the incremental update and random access benefits if the schema were simple.
It’s easy for the OpenDocument case to just say “use plain text files, images and git”, but I’m convinced that using sqlite or designing your own careful file format is a good solution for applications.
I’ve been using SQLite as the application format for various projects. It is easy to use because it is ubiquitous. I can package SQLite myself; I can use SQLite from the distro; I can update as I go; I don’t need to worry about saving took long time. As long as I stick with the basics, it works everywhere.
That has been said, it is interesting that in many places, I do find the application format end-up as a simple key-value pairs, or a web (tree?) of hierarchical objects. Both SQLite can model, however, both are not tabular per-se. Something like HDF5 seems model better for my hierarchical objects. However, packaging HDF5 with various wrappers is a challenge by itself, and SQLite has APIs I am already familiar / enjoying with.
Did you try sqlite lsm extension? It is available in sqlite3 tree and you can use it with a sqlite database (or standalone).