[Bug]: Can't update submodel with database support enabled although returned status is OK

[heidrjeSICKAG]

Contact Details

No response

Describe the bug

I'm trying to update a value of a single property of a submodel. I tried different approaches like
PUT /submodels/{submodelIdentifier} or
PATCH /submodels/{submodelIdentifier} as well as directly on the value itself via
PATCH /submodels/{submodelIdentifier}/submodel-elements/{idShortPath}/$value
If the database is enabled the data isn't persisted although the server returns a 204 status code. As soon as the database support is disabled the requests works as expected and subsequent GET requests on the submodel and the Web UI return the updated value.

To reproduce

1. Enable database support with the --with-db start parameter.
2. Issue update request for a submodel or a value
3. Data hasn't been updated

Screenshots

No response

Expected Behaviour

Data should be updated and persisted with database enabled.

Version

No response

Operating System

Linux

Relevant log output

No response

[aorzelskiGH]

Since this is not implemented in the code actually, it is a feature request, although it looks like a bug.