@heluecht Some ORM systems have resolved this particular issue by saving the values as they were when the Entity was instantiated from the database as “clean”, and setting the fields that have been updated as “dirty”. Then when persisted, they only use the “dirty” fields. I do think we’d easily be able to implement a version of this clean (coming straight from the DB)/dirty (needs to be persisted) concept.