Bug
New occurrence with already existing value not inserted
Issue description
Given a topic T1 with an occurrence O1 with value V1. Further a user edits T1 and replaces V1 by V2 in O1 and adds a new occurrence O2 with the value V1. After saving, T1 has only one occurrence with value V2. It should have two.
This affects associations and names as well.
Developer comments
This is caused by a duplicate item check before inserting. Only in this case the item is for sure new.
Quite amazing that this has not surfaced yet. I discovered it when working [9734, on this issue].
Respecting the incoming updates to statements, so that the new item is no longer ignored as a duplicate.
|
Work sessions2
Start |
2020-10-23T17:20:51
|
End |
2020-10-23T19:20:30
|
Participant |
Robert Cerny
|
Start |
2020-10-23T20:45:15
|
End |
2020-10-23T21:02:58
|
Participant |
Robert Cerny
|
|
We are sorry
This page cannot be displayed in your browser. Use Firefox, Opera, Safari, or Chrome instead.