feat: add secure -C option to support VACUUM INTO as an alternative to .backup command - #8
Merged
Merged
Conversation
…o .backup command
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi everyone,
Issue #7
It adds support for using VACUUM INTO as the backup command.
I introduced the SQLITE_BACKUP_COMMAND environment variable together with the -C / --command CLI option. The default is still .backup, so the current behavior doesn't change unless a different command is explicitly selected.
To avoid running arbitrary SQL, the input is validated and only .backup and VACUUM INTO are accepted.
If VACUUM INTO is requested but the backup falls back to a plain SQL dump, a warning is written to the log.
Ciao,
Luca