When entity with non-nullable fields is persisted prior these fields are filled, the insert operation is added to the action queue immediately, even though HHH-5472 taken great effort to make sure this doesn't happen for non-nullable transient entities.

Would it be possible to combine update action (which is generated due to field being dirty after it has been filled) to preceding insert action in order to avoid ConstraintViolationException.