Univention Bugzilla – Bug 45486
UDM objects aren't robust against multiple operations
Last modified: 2020-06-22 18:37:16 CEST
UDM objects aren't robust against multiple operations, e.g. If you .modify() an object twice some extended attributes might be removed. See also Bug #45468 comment 3 and comment 4. We should make sure that after any operation like create(), modify(), move() and remove() the internal state is correct again.
I think that'd be rather expensive, as it'd require fetching the object again and running open(). At least when UDM hooks are registered for a module. So I suggest to make this optional, by for example adding a "refresh()" method.
Jeah, I thought about a reopen() method. We could fetch the object again with a post-read-control as we already do in the S4 Connector.