[KATC/IndexedDB] Adjust strict mode for opening leveldb-backed indexeddb #1800
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.
Previously, we were using strict mode
StrictAll
:Several of these options prevent the database from being opened at all if corruption is present. It is more reasonable for our usecase to at least attempt to read the data out of the database. I have therefore opted to swap to
StrictRecovery
only (If present then leveldb.Recover will drop corrupted 'sorted table'
).