Fast writer always fully replaces locators

Issue description

With the recent changes for transferring modules (schema & code) from an origin store to other stores, an lurking problem has surfaced. It is actually a problem of topic map writing. Given a store S1 containing a topic T1 with a set of identifiers I1, and a topic map in a file also containing T1, but with different set of identifiers I2, with I2 and I1 sharing at least one identifier, after the import T1 will have only S2, all other identifiers from S1 are gone. Thus there is always a full replace.

Developer comments

This problem surfaced in the work on [13147, modules], since the system topics are transferred with just two subject identifiers, one is the orginial one from the system store, the other is the local subject identfier from the module origin. This glue is necessary in order to map [13351, system topics to a differnt ids]. Even if we would equip the topic with all identifiers from the origin store, the topic in the target store might use modules from differnet origins which all added their local subject identifier. So these would be lost.

This might affect other items as well, then only for the item_identifiers.

Reporting date

2024-08-12

Reported by

Robert Cerny

Resolving date

2024-08-13

Resolved by

Robert Cerny

Resolved in version

Topincs 10.0.0 - next major release

Related to4

Exporting jtms(Change)

Modules(Enhancement)

Handling of system topics in modules(Change)

Changing subject identifiers does not work(Bug)

Work sessions

Start	2024-08-13T13:05:23
End	2024-08-13T14:37:27
Participant	Robert Cerny