本文介绍如何通过将session.saveOrUpdate()方法替换为session.merge()来避免NonUniqueObjectException异常。此异常通常发生在尝试同时附加两个相同类和标识符的对象到同一个会话中时。使用merge()操作可以有效避免此类问题。
把session.saveOrUpdate(role); 改为
session.merge(role); 就搞定了
官方的user faq
I called saveOrUpdate() or update() and got a NonUniqueObjectException!
The session maintains a unique mapping between persistent identity and object instance, in order to help you avoid data aliasing problems. You cannot simultaneously attach two objects with the same class and identifier to the same session.
The best way to avoid any possibility of this exception is to always call saveOrUpdate() at the beginning of the transaction, when the session is empty.
In Hibernate3, you can try using the merge() operation, which does not reattach the passed instance
session.merge(role); 就搞定了
官方的user faq
I called saveOrUpdate() or update() and got a NonUniqueObjectException!
The session maintains a unique mapping between persistent identity and object instance, in order to help you avoid data aliasing problems. You cannot simultaneously attach two objects with the same class and identifier to the same session.
The best way to avoid any possibility of this exception is to always call saveOrUpdate() at the beginning of the transaction, when the session is empty.
In Hibernate3, you can try using the merge() operation, which does not reattach the passed instance
扫一扫
758
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
