@giuseppe_aceto@scholar.social
Post #2571961
2025-08-08 08:02 UTC
@goetz@freiburg.social @jpmens@mastodon.social @gereon@chaos.social I appreciate the joke, but I find it quite enlightening, because it made me realize the following.
Processing a single-file encoding of a database is not technically different from processing a compressed archive: the second is just a very specific use case for the first. It's just a matter of interface.
Want it to be MORE Unix? implement both sqlite3 and zip as interfaces to an underlying single-file relational database manipulation library (applies to ALL file formats).
Replies (1)
-
@goetz@freiburg.social 2025-08-08 09:43
@giuseppe_aceto@scholar.social @jpmens@mastodon.social @gereon@chaos.social You can see a ZIP file as a (very special, or bad, depending) database, as much as you can see the file system itself, where the ZIP file is stored on, as a database. So a ZIP file on a filesystem is like a MySQL blob within a PostgreSQL table. Change my mind.