Change
Handling of missing dobjects
Issue description
If a store uses dobjects, missing dobjects should cause no invalid or incorrect data. At no point should computation be continued and attempted when a dobject is missing. Therefore a missing dobject should cause an exception.
Developer comments
It was considered to throw an exception when a dobject is missing, but this caused havoc in regression tests.
Additionally if a request creates a new topic, either .save through form or a POST service, the dobject is currently only created at the end of the request. All triggers are therefore working on a tobject without dobject. This is not true. The dobject is created before the triggers run in package saving.
After much consideration and failed change attempts: a missing dobject *should* cause an exception but not under all circumstances.
A missing dobject is an exception, if and only if
* dobjects are active in the store (obvious)
* autocommit is off.
This was reverted temporarily to simply log the problem, since [14018, this issue] surfaced.
|
Work sessions3
| Start |
2025-04-29T10:38:36
|
| End |
2025-04-29T11:41:01
|
| Participant |
Robert Cerny
|
| Start |
2025-04-29T13:43:16
|
| End |
2025-04-29T18:20:25
|
| Participant |
Robert Cerny
|
| Start |
2025-05-01T12:43:44
|
| End |
2025-05-01T15:21:28
|
| Participant |
Robert Cerny
|
|
We are sorry
This page cannot be displayed in your browser. Use Firefox, Opera, Safari, or Chrome instead.