There is a utility from the SQLite devs that can archive a directory as a SQL file. I'm fairly new to the whole SQL world (more of a NoSQL guy myself due to work environment), but from what I read in the docs, sqlite-zstd could be used to create a solid-ish archive, generating dictionaries by extension, for example. Not true solid compression, but there would be some shared information between files I guess, instead of the current method of simply passing each one through zlib independently.
Am I reading this correctly? Could this be a common enough use case to warrant a script that automatically compresses a SQLite archive with zstd?
There is a utility from the SQLite devs that can archive a directory as a SQL file. I'm fairly new to the whole SQL world (more of a NoSQL guy myself due to work environment), but from what I read in the docs, sqlite-zstd could be used to create a solid-ish archive, generating dictionaries by extension, for example. Not true solid compression, but there would be some shared information between files I guess, instead of the current method of simply passing each one through zlib independently.
Am I reading this correctly? Could this be a common enough use case to warrant a script that automatically compresses a SQLite archive with zstd?