This repository was archived by the owner on Dec 9, 2021. It is now read-only.
Open
Conversation
This offers parity with KeePass
jsoref
force-pushed
the
search-groups
branch
2 times, most recently
from
8a60d75 to
9637f93
Compare
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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 offers parity with KeePass
[I haven't tried running this. It's more of a conceptual explanation of what should be done.]
Basically: we have a KeePass database which has:
Org
. Datacenters
.. Foo Center
..x Admin Account
..x User Account
.. Bar Center
..x Admin Account
..x User Account
.x Sandy Center Access
(items w/ x are entries, all items w/o are groups)
I can search for "Sandy" today in KeePassX, but my coworker has no trouble searching for "Bar" and "Foo" -- because he uses KeePass.
I agree with his KeePass database structure, the hierarchy makes a lot of sense.
I can work around this problem by stuffing metadata into Entry fields (especially URL). But the database is fairly large, and adding that metadata is busywork.