Sure those are differences. I really mean: how does something deliberately designed to be a file system in a file compare to SQLite being used that way?
It does not, unless you use SQLite in a read-only manner which doesn't make much sense anyway.
BTW. There's nothing in SquashFS that makes it "a filesystem in a file". You can use it directly on a device (and it's often used this way), and you can use many other filesystems in a file just as well.
SquashFS is read-only and requires elevated permissions to mount, but also presents as a true filesystem.
Sure those are differences. I really mean: how does something deliberately designed to be a file system in a file compare to SQLite being used that way?
It does not, unless you use SQLite in a read-only manner which doesn't make much sense anyway.
BTW. There's nothing in SquashFS that makes it "a filesystem in a file". You can use it directly on a device (and it's often used this way), and you can use many other filesystems in a file just as well.
> but also presents as a true filesystem.
As does:
https://github.com/guardianproject/libsqlfs
https://github.com/narumatt/sqlitefs
(I know nothing about these, just got them from a quick search)