DOC: added a hint/warning for upgrading from <0.6.0 and a general warning for unique uids#125
Merged
violoncelloCH merged 1 commit intonextcloud:masterfrom Feb 19, 2020
DJCrashdummy:patch-1
Merged
DOC: added a hint/warning for upgrading from <0.6.0 and a general warning for unique uids#125violoncelloCH merged 1 commit intonextcloud:masterfrom DJCrashdummy:patch-1
violoncelloCH merged 1 commit intonextcloud:masterfrom
DJCrashdummy:patch-1
Conversation
…for unique uids - finally i added a hint/warning for upgrading from <0.6.0 to manually rework the database according to #64 (comment) since it is the clearest statement i found about this topic (and it seems to work for a bunch of other guys and myself). - additionally added a general warning to make sure to have unique `uid`s.
DJCrashdummy
changed the title
violoncelloCH
approved these changes
Feb 19, 2020
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
2 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.
finally i added a hint/warning for upgrading from <0.6.0 to manually rework the database according to Document recent database changes for IMAP-Backend #64 (comment) since it is the clearest statement i found about this topic (and it seems to work for a bunch of other guys and myself).
since there is no other doc or wiki i added it directly to the IMAP part of the main readme... anywhere else it would be pretty useless.
maybe it is enough to close Document recent database changes for IMAP-Backend #64...?
additionally added a general warning to make sure to have unique
uids.