hbm 3.1 core / 3.b7 ann

hbm is cascading updates on all children in a birdirectional @OneToMany when an attribute of the parent is updated....i.e update one parent with 20 child objects in a collection when no attributes of the children have changed, i.e. 21 records updated on the database whereas I was expecting only the parent records change to be persisted.

hbm compares by value, even if CascadeType=PERSIST is set on the parent getChildren(), I would expect the changed values in the children to be persisted if any child attributes have changed which they had not?

any explanation welcomed
thks

please ignore ...user error !
;-)

Just curious what your user error was? I am experiencing a similar issue when I add a new Address to a previously persistent User instance. When I add the Address to the User and then pass it to Session.persist(), I see that Hibernate inserts the new Address, but also loads up all of the other assocations - which are never used or called in the transaction. This is not the behavior when I was seeing when using the XML mapping files so I'm very curious is there is a simple solution. Thanks!

Ryan-

Ryan,
hbm does not compare by value for collections.

Well, it depends on the type of collection used. I happen to be using a Set and the values will be compared as to not allow duplicate values. If Hibernate needs to load the items in the Addresses Set of my User instance in order to identify duplicate instances. That is the expected behavior and I understand that.

However, what I am seeing is that other Sets such as the User's phone numbers, email addresses and other one-to-many collections are being fully initialzed when I add an Address to the User and pass the user to Session.persist(). This is behavior that I have not encountered when using the XML mappings and calling Session.update().

Ryan-

this is fixed in later versions

Thanks for the info Emmanuel! I'll be sure to check out the latest.

Ryan-