xkb

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

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.

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)

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

+1 In heterogeneous environments it would come in extremely handy for Devops (deployment of DDL, DCL, DML scripts) ...provided a rich log upon sql instructions submitted could be generated.

Hello, I'm +1 on that feature request with optional group by groups (?)