上一篇
下一篇
07-08
22
ObjectNotFoundException: No row with the given ide
作者:Java伴侣 日期:2007-08-22
郁闷了好久，终于在goole上找到了错误原因
ObjectNotFoundException: No row with the given identifier exists
Where it can occur:
This might occur if you try to load a non-proxied object with session.load() or you load a proxied object and later access the proxy. It may also occur when loading mapped collections which are not eagerly fetched.
What it means:
This means just what it says - Hibernate expected to have a row with a certain id in the database, and did however not find it.
How it can be caused:
Wrong id for load
If you are using a nonexistant id for a load(), you will get this exception. Note that if you are using proxies, this may occur later on, when the proxy is first "broken".
Broken foreign key relationships
If you map for example a many-to-one relationship, and the table containing the objects on the "many" side contains a foreign key to a non-existant row of the "one" side table, you will get such an exception. This will only happen if the collection is not fetched eagerly.
Reusing a session across multiple transactions
The hibernate session internally memorizes some state. For example it internally stores ids which it assumes are already deleted from the database. So if you make the session believe somehow an object with a certain id has been deleted, and later try to load it again, you will get this exception without Hibernate even trying to access the database. So be careful with that.
How it can be fixed:
* Check the ids you are using for load
* Validate your foreign key relationships - the database should already maintain such integrity constraints.
* Beware of multiple transactions within a single session. Try to stick to "one session, one transaction" rule. Especially do not reuse sessions after an HibernateException.
也就是是说关系数据库一致性遭到了破坏，找到相关表，就可以解决了
ObjectNotFoundException: No row with the given identifier exists
Where it can occur:
This might occur if you try to load a non-proxied object with session.load() or you load a proxied object and later access the proxy. It may also occur when loading mapped collections which are not eagerly fetched.
What it means:
This means just what it says - Hibernate expected to have a row with a certain id in the database, and did however not find it.
How it can be caused:
Wrong id for load
If you are using a nonexistant id for a load(), you will get this exception. Note that if you are using proxies, this may occur later on, when the proxy is first "broken".
Broken foreign key relationships
If you map for example a many-to-one relationship, and the table containing the objects on the "many" side contains a foreign key to a non-existant row of the "one" side table, you will get such an exception. This will only happen if the collection is not fetched eagerly.
Reusing a session across multiple transactions
The hibernate session internally memorizes some state. For example it internally stores ids which it assumes are already deleted from the database. So if you make the session believe somehow an object with a certain id has been deleted, and later try to load it again, you will get this exception without Hibernate even trying to access the database. So be careful with that.
How it can be fixed:
* Check the ids you are using for load
* Validate your foreign key relationships - the database should already maintain such integrity constraints.
* Beware of multiple transactions within a single session. Try to stick to "one session, one transaction" rule. Especially do not reuse sessions after an HibernateException.
也就是是说关系数据库一致性遭到了破坏，找到相关表，就可以解决了
文章来自: 
引用通告: 
Tags: 
相关日志:
评论: 0 | 引用: 0 | 查看次数: 917
发表评论
