[hibernate-dev] More fun with merging : non-updatable fields

Christian Bauer christian.bauer at jboss.com
Wed Sep 27 13:14:07 EDT 2006


On Sep 27, 2006, at 6:43 PM, Emmanuel Bernard wrote:

> This is consistent with the way saveOrUpdate works

And it's perfectly reasonable behavior. If I modify a field value,  
then merge, then take the instance returned by merge, I expect that  
the value is still there in the merged result. That has nothing to do  
with the update/UPDATE behavior of Hibernate.




More information about the hibernate-dev mailing list