This is 3.0.5.

If I have a parent that has a set of children, and the one-to-many is mapped with cascade=save-update, is it normal for Hibernate to issue a SQL update for all the children in the set when performing an update on the parent, even though none of them have actually changed? I used to think that was just the way <set> mappings worked, but Gavin's response in this thread has me wondering. As far as I know my equals() and hashCode() work correctly, but I do call retainAll() and addAll() on the collection(s).

What have been your experiences?

Put a breakpoint in the equalsSnapshot method of the PersistentSet class and you can see why hibernate think your objects are modified