Resolve references before copying entries to another database

[spi43984]

Overview

REF for username/password in other (but also already opened) DB

Examples

1. clone entry, create in clone REF: for username and password for original entry in same DB
2. clone's username and password refer to correct values
3. move the clone to another also opened db
4. clone's username and password don't refer to correct values anymore, they're just empty

Context

I open a master DB. In it a slave DB is additionally opened via theAutoOpen group. So if I open the master DB, the other one is "daisy chained". I'd like to use REF for entries not only in one DB but across these DBs.

[phoerious]

Duplicate of #7449

[spi43984]

It is not a duplicate as this is a feature request and the other one a closed bug report.

[phoerious]

WONTFIX means we are not currently planning to implement this feature, so please do not open duplicate reports. Thanks. There is no point in having hundreds of unlikely feature requests lurking in the deeps of our issue tracker.

[droidmonkey]

Well we could set it up so that when an entry is dropped on a different database it resolves and bakes in the references prior to being attached to the new database.

Databases are independent from each other, even if opened from one another. That is by design and won't change. We will never implement cross database references. What you want is handled by keeshare though.

[phoerious]

That is something we can do, but keeping references across databases causes more harm than anything and is not worth the trouble implementing. Besides simple drag-and-drop (which requires no real knowledge of other databases), we have no cross-database logic at all, this would require huge rewrites of our database handling.