Remove resolve duplicate keys dialog#4696
Merged
Merged
Conversation
Member
|
Well, however on import there should be a warning and the option to resolve duplicate keys. It's essential to discover duplicates |
Member
Author
|
@Siedlerchr such a feature wasn't implemented (the only check was when opening a database) and is obsolete with my other PR #4692, where now keys are automatically generated for every imported entry. Duplicate entries are also highlighted in the import dialog. |
Member
|
Okay, then I see no problem! |
Siedlerchr
approved these changes
Feb 23, 2019
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
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.
Fixes #4614
Removes the resolve duplicate keys dialog. This feature is made obsolete by the integrity check and the user can generate new keys very simply (for all entries or only for the duplicated ones) through the entry editor and/or menu.