Bug
Autocommit off: replacing an uncommited adjunct counter player fails
Issue description
Given a service call where two uncommited topics T1 and T2 are created and both are set as a player of the same old topic T. This causes the second set call to throw an exception since the current player T1 is checked if T1 can be modified or if it is frozen. But this check fails since the frozen check does not consider uncommited topics.
Developer comments
Only the player of the first set call needs to be new, the second one can be old or new.
This only affects counter player that are adjuncts.
|
Work sessions2
| Start |
2025-04-01T14:38:08
|
| End |
2025-04-01T16:26:20
|
| Participant |
Robert Cerny
|
| Start |
2025-04-02T08:00:00
|
| End |
2025-04-02T11:21:35
|
| Participant |
Robert Cerny
|
|
We are sorry
This page cannot be displayed in your browser. Use Firefox, Opera, Safari, or Chrome instead.