@jeremyruston – Nice work!
I am curious about some design decisions. So here are the questions:
-
Why did you decide to use SQLite as a backend, instead going with a “file based” approach or an other database?
-
Since the SQLite database file is one large file. What’s the limit of the database-file size?
-
Did you find good performance data for a database that represents a specific usecase as TiddlyWiki?
-
What’s about the hardware requirements for SQLite?
-
What’s about “human readable” backups? aka files. IMO there is a reason, why users like files
-
Databases usually do not delete content. They mark it as deleted and keep it.
6.1 Is that also true for SQLite? (found an answer - below)
6.2 Is it possible to “purge” unused / deleted data from the database? (It’s about privacy concerns)
I did find an answer for 6ff (according to ChatGPT) –
- SQLite does mark deleted data-space as available. So it will be overwritten by new data over time.
- There is a purge command, which is called “vacuum”
-mario