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.
Add a new option to create a database backup file on version changes. This is handy for extreme cases where a bug is introduced, or user have another reason to downgrade. However, some schema migrations may not be backward compatible, and with an automatic copy of the database file in case the
revision
changes, it will allow path to recover the database to that point and continue working with the previous version.File naming is
tg-spam.db.<revision>
, i.e.,tg-spam.db.master-77e0bfd-20250107T23:17:34
. The file name is a bit confusing because it means "backup prior to the version," but for now, this is the best I can think of.