When using @DynamicUpdate, when a field within an embedded object of an entity is changed, all the fields of this embedded object are included in the update.

I intend to use @DynamicUpdate in combination with @OptimisticLocking(type = OptimisticLockType.DIRTY) in order to reduce the number of StaleObjectStateExceptions. However, with the current behavior, this stragety is not as effective as I hoped, since concurrent modifications of different columns of the same embeddable may still cause the exception.