Two records with the same key (enhancement)

[gdmiron]

Often many users encounter the message of two records with the same key. Either they select two or more sources or in someway duplicates are added. In this situation the program does not open the project and often the user doesn't know what to do. A potential new behavior is to show the message with the two records and source database file and let the user decide if to take first "yes" take second "no" or "cancel" (don't open the project).

We can discuss if this makes sense.

[sdmytrievs]

A I remember, it is impossible to insert two records with the same key into one file. If you have such examples will be very good for the test.
It is possible if in the project there are two or more files for one record type.
Could you give me such examples? I can realize the second state (with two files).

[gdmiron]

We should still leave this as impossible to have two records with the same key into one file. What i suggest is to give the users the possibility to chose which of the two records to keep.

When this error appears it means that in GEMS by mistake or intentionally two database files were selected that contain the same record. For example:
dcomp.db1.rec.aqueous.pdb
dcomp.db2.rec.aqueous.pdb

In this case the message should be ´Two records with the same key. "Yes" Take record from db1 or "No" take record from db2.´ Also with options Yes to all and No to all.

If the user click No to all then all duplicate records are taken from db2.

[gdmiron]

Example of project having the issue: https://github.com/user-attachments/files/21009642/CFAS_SUPa.zip

[sdmytrievs]

About problems in CFAS_SUPa. In this project broken phase index file. In the header 30 records, but present only 28. When trying to read the last two, the key did not change and tried to save the same record.
I changed the error message to "file_name+ " index file read error."
The user needs to compress the file to restore the index.

[sdmytrievs]

About:
Error the message of two records with the same key when project open if there are two database files that contain the same record.

This error happened when reading the index file, we cannot any deletion or renaming here any records.

If we ignore the second file when opening the project, we do not read all records from it, and get a lot of messages about changes in the project, and break all systems.

Better solution back to edit db mode and delete one of the records.

I can add a special mode of reading the index file, when a duplicate record will be saved with a different last key field, but not change the key in db. But it is aggressive changes in the worked and debugged functions of db.

[gdmiron]

When having databases with close names tow records error can appear.

In my case I want to make a project with cemdata26 and psinagra2020 (attached files)

after selecting elements. Two records with the same key error appears due to the two "cemdata" with red in the screenshot (I only select cemdata26 but the error appears nonetheless).

cemsa.zip

[sdmytrievs]

Fixed the error opening 'cemdata' if selected 'cemdata26'.
But 'sdref.3rdparty.cemdata26' and 'sdref.psinagra2020.main' have records with same key

[sdmytrievs]

sdref_nagra2000.txt

sdref_cement26.txt

[gdmiron]

dcomp.3rdparty.cemdata.ss.cash+.ver21.00.zip

[gdmiron]

dcomp.3rdparty.cemdata.ss.cash+.ver21.00.zip

managed to fix this by export the records to backup json and making new db files from backup json import - Seems the files had some broken index or something.