Add methods to perform migration to new major SQLCipher after setting a key #972
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.
This change adds
keyAndMigratemethods which perform "PRAGMA cipher_migrate;" callimmediately after calling
sqlite3_key_v2This call is needed to open the database files created in older major SQLCipher version (e.g. 3.x.x)
by newer SQLCipher version (e.g. 4.x.x).
(see #908)
These calls should be performed only once, when opening older database files for the first time.
See https://www.zetetic.net/sqlcipher/sqlcipher-api/#cipher_migrate
and https://discuss.zetetic.net/t/upgrading-to-sqlcipher-4/3283 for more details regarding SQLCipher upgrade