Bug
Auto commit off: Duplicate typed but otherwise empty topics created in nested trigger
Issue description
A production system creates strange topics, which are typed but otherwise have no information on them. They are created in a trigger. There is multiple triggers running during this form save. A topic of the same type is created correctly as well. So these are duplicates.
Developer comments
This store is a copy of a store from a previous year where everything worked ok.
This is one of the rare cases in a production system where a trigger triggers a trigger. In this case an item trigger TR1 fires on an occurrence event and creates a topic T1 which as associated with an old topic T2. This triggers an item trigger TR2 on a role event. This trigger create a topic T3 and associates it with T1.
This surfaces only under very peculiar circumstances. Given a trigger TR1 creating a topic T1 and an association A1. The creation of T1 triggers another trigger TR2. This trigger runs after T1 has received its system id, but A1 still uses the the temp id of T1, since A1 at this stage is not yet persisted. As long as TR2 does not use A1, everything is fine, but as soon this association is traversed via a get call, this bug occurs. It was fixed by remembering the temp id a little longer and returning the right tobject to TR2.
|
Work sessions3
Start |
2024-04-24T13:25:08
|
End |
2024-04-24T14:53:29
|
Participant |
Robert Cerny
|
Start |
2024-04-26T09:06:40
|
End |
2024-04-26T10:59:43
|
Participant |
Robert Cerny
|
Start |
2024-04-26T11:42:03
|
End |
2024-04-26T13:05:12
|
Participant |
Robert Cerny
|
|
We are sorry
This page cannot be displayed in your browser. Use Firefox, Opera, Safari, or Chrome instead.