I am considering using SQLite as an application file format, for many reasons, of which the first is "free" ACID semantics. (Actual cost paid in performance, of course.)
My application could also be served well by using a database format because the information users want to know might be open-ended and possibly supplied with good SQL queries.
The SQLite authors claim [1] that SQlite is great for an application file format, but claims are weak. Does anyone have any experience that supports or refutes that claim?
Also, I would prefer a database with static typing, but I am willing to reconsider if SQLite's manifest typing [2] is not a problem for performance, as it seems it might be. Is it a problem?
If I do use SQLite, is there anything else I should know?
(And to head off questions, my application is a specialized Version Control System.)
My application could also be served well by using a database format because the information users want to know might be open-ended and possibly supplied with good SQL queries.
The SQLite authors claim [1] that SQlite is great for an application file format, but claims are weak. Does anyone have any experience that supports or refutes that claim?
Also, I would prefer a database with static typing, but I am willing to reconsider if SQLite's manifest typing [2] is not a problem for performance, as it seems it might be. Is it a problem?
If I do use SQLite, is there anything else I should know?
(And to head off questions, my application is a specialized Version Control System.)
[1]: https://sqlite.org/appfileformat.html
[2]: https://www.sqlite.org/different.html#typing