Hibernate session.merge(persistingObject) Vs session.saveOrUpdate(persistingObject)

Hibernate provide two techniques to deal with save and update functionality,
As per those techniques it first checks the instance in db, if
It is already persisted in that database, if that is the case then it
will simply persist the updated fields into DB otherwise it will persist
the new instance in to DB.

session.saveOrUpdate(persistingInstance):It also persist the new instance in to DB
and update the already persisted instances.
Insert the data if the primary key is not exist.

Problem:In some scenario's you might face the issue of
NonUniqueObjectException : message
"a different object with the same identifier value was
already associated with the session."

Technically before persisting in to db it first check in to the Hibernate cache,
and by any reason if that
object is present in cache then you will get the above exception.

So by remedy of the above issue we can use session.merge(persistingObject):
It is directly checking in to your database not in Hibernate cache,
so the above error will never ever arise.

Recommendation:session.merge();