Hibernate Team |
|
Joined: Tue Aug 26, 2003 12:50 pm Posts: 5130 Location: Melbourne, Australia
|
We don't think its useful and don't recommend it. It is there for the sake of completeness, since we now aim to be a "complete" ORM solution.
It *does* let you avoid the dreaded NonUniqueObjectException, but at the cost of performance.
(Actually NonUniqueObjectException is your friend. It tells you that you are risking possible loss of some changes, so in this sense saveOrUpdateCopy() is less "safe".)
It may also be used as an alternative to select-before-update if you are trying to avoid unnecessary SQL UPDATEs due to lack of a snapshot.
|
|