Heal references of references when the intermediate is deleted

[rugk]

I guess when you reference references it may not result in good things…

Steps to Reproduce

1. Duplicate an entry.
2. Look at the ref ID, e.g. of the username. (Let's say it is "A")
3. Duplicate that entry again.
4. Now look at the ref ID (of the same, i.e. the username obviously).

Expected Behavior

Ref ID should be A.

Current Behavior

Ref ID is a new one (say "B"), so I assume this is the reference to the reference entry.

Possible Problem

E.g. what happens if I delete the first reference?

Context

Basically this came up when I tried these references, see #2527.

Debug Info

KeePassXC - Version 2.3.4
Revision: 6fe821c

Bibliotheken:

• Qt 5.11.1
• libgcrypt 1.8.3

Betriebssystem: Fedora 29 (Workstation Edition)
CPU-Architektur: x86_64

[rugk]

Why closed? And why is this a new feature? It's rather a kind of a bug is not it? As said, if you delete the original reference of a reference, things likely break… this should be prevented…

[droidmonkey]

Why should it be prevented? It is perfectly reasonable and aligns with KeePass spec. If you choose to delete something in the reference chain, that is technically on you. Ideally the application would "heal" the reference for you.

[rugk]

Ideally the application would "heal" the reference for you.

Okay, so if it does not do that, that would be a/the feature request (here), would not it?

[droidmonkey]

Sure, I can go with that.