no backup to have the ability to fix a damaged database#2780
Closed
hannesa2 wants to merge 1 commit into
Closed
Conversation
hannesa2
changed the title
Otherwise even after a deinstallation of the app, a damaged database is still on the filesystem and a reinstall doesn't help overwrite allowBackup
hannesa2
force-pushed
the
AbilityToFixDestroyedDatabase
branch
from
e581e80 to
77ec3ed
Compare
Contributor
Author
|
I guess, with #2779 or a similar solution it's no more necessary. |
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
1 participant
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.
Otherwise even after a deinstallation of the app, a damaged database is still on the filesystem and a reinstall doesn't help.
But maybe you fix it with a new database version, then this pull request is obsolete