Dobjectification in FastWriter incomplete

Issue description

In FastWriter dobjects for new topics should be created right away so that triggers use the dobject and avoid MySQL. This works well for the form, but otherwise not so much. If the packge is the result of a computation in a service, this has never been a problem, since in this case the dobject is already present. But in the case at hand the package is a topic map in a module. It would be wrong in this case to simply claim it comes from the form, since this would cause the form triggers to run.

Developer comments

Another intresting question in this case is: what happens if there is an exception in the an after form trigger? Is the created dobject deleted.

It was confirmed that the dobjectification in FastWriter was incomplete and the error was fixed. Several tests were added to check the correct behavior. In addition a mechanism was put in place that dobjects are removed from the filesystem on a rollback independently of whether they are present in memory or not. It can be that a form save creates two topics but a trigger is only run for one of them and ends in an exception. Still both dobjects must be removed.

Reporting date

2025-05-21

Reported by

Robert Cerny

Resolving date

2025-05-21

Resolved by

Robert Cerny

Resolved in version

Topincs 10.0.0

Caused

Module import fails because dobject is null(Bug)

Work sessions2

Start	2025-05-21T12:56:43
End	2025-05-21T16:30:35
Participant	Robert Cerny

Start	2025-05-22T08:00:00
End	2025-05-22T10:01:13
Participant	Robert Cerny