Repository navigation
keep user_version when Set Encryption - #846
Merged
Merged
Conversation
Set user_version of the new db to current user_version. Otherwise user_version would be set to 0.
Member
|
Thanks @bssthu. 😄 @MKleusberg Do you have time to look at this? |
Member
|
Thank you, @bssthu! Good work spotting this issue and thank you so much for even providing the proper fix 👍 If you should ever feel like fixing some more bugs you're very welcome to open more PRs 😉 |
vtronko
pushed a commit
that referenced
this pull request
Dec 29, 2016
Set user_version of the new db to current user_version. Otherwise user_version would be set to 0.
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
3 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.
Set user_version of the new db to current user_version.
Otherwise user_version would be set to 0.