Given the model:
container foo { leaf bar { type string; } }
performing the following operations:
tx.delete(foo); tx.write(foo/bar, value);
will not result in the leaf being present. This seems to be operation merging bug coming from automatic container lifecycle: previously this stacking would not have been allowed, as the parent does not exist.
With automatic lifecycle, though, the container is transiently created and therefore this stacking is completely valid – performing these operations in two separate transactions produces a result where bar is present.
- is duplicated by
-
MDSAL-420 LazyDataObjectModification reports incorrect results
- Resolved