Re-write folders order in database when they are automatically sorted #1797
Conversation
This file contains 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
Through locking of messages.db by opening it in an utility application while simultaneously running Vienna, I ended up with some of my folders having next_sibling equal to folder_id … As a precaution for when Vienna falls back to alphabetical auto sorting of folders, ensure that we have coherence of first children and the succession of siblings.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Through locking of messages.db by opening it in an utility application while simultaneously running Vienna, I ended up with some of my folders having next_sibling equal to folder_id …
As a precaution for when Vienna falls back to alphabetical auto sorting of folders, ensure that we have coherence of first children and the succession of siblings.