inserting all Field References (by uuid) to a new entry to mimmic symlink

A lightweight and easy-to-use password manager

Brought to you by: dreichl

#2881 inserting all Field References (by uuid) to a new entry to mimmic symlink

Milestone: KeePass

Status: open

Owner: nobody

Labels: None

Priority: 5

Updated: 2024-05-30

Created: 2024-05-29

Creator: xkb

Private: No

Hello,

By reading the fine manual, I saw that F.R. like #1683 Link to group or entry (or say : creating full ref symlink) was rejected (too bad)

...so may I suggest inserting all Field References (by uuid) to a new entry in order to save on the burden of inserting every single one in every single field.

It serves the same purpose of a link : oftentimes, an entry may be relevant to several different parts of the tree (say, by technology on one hand but also per project on another one).

Thanks

Discussion

Paul - 2024-05-29

"All" being from a single entry, or every UUID of every entry?

cheers, Paul

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- xkb - 2024-05-29
  
  Hi Paul,
  I was thinking single entry : you just want some entry to basically appear in some other(s) place(s) but only to update master reference in order to update all fields of all symlinks (or say : clones)
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

wellread1 - 2024-05-29

oftentimes, an entry may be relevant to several different parts of the tree (say, by technology on one hand but also per project on another one).

Tags might serve that purpose equally well.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- xkb - 2024-05-29
  
  Hello WellRead1,
  You answer makes sense and I might leverage those tags to index my entries through alternate classification (than just hierarchical tree)
  However, tags are not as rich as multiple hierarchies (when you can play with symlinks) and won't offer same semantics as, for example, moving entries or a whole folder from branch to branch.
  I guess both tags AND links/refs would be the graal.
  Thx anyway.
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

wellread1 - 2024-05-30

Field references are brittle. If the primary entry is deleted by accident, all entry data for the entire set of related entries is lost.

Field references will probably never apply to custom fields because changing the custom field name breaks the reference.

Field references are awkward to trace.

Tags don't suffer any of these problems because there is only one entry that can have multiple tags.

Last edit: wellread1 2024-05-30
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- xkb - 2024-05-30
  
  I do agree with most of what you say which doesn't make refs irrelevant, nonetheless (added, not replacing)
  
  Symlinks exist in hierarchical file systems, and they bear all the mentioned weaknesses.
  However, blob storages used to implement only tags until they re-implemented nested-folders structured, keeping tags along ; and that's quite a comfort.
  
  Think it as belt AND suspenders
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Log in to post a comment.