[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2753?page=c... ] Jean-François St-Germain commented on HHH-2753: ----------------------------------------------- Yes what, it's fixed? It's normal? I get the same problem, this is a totally unacceptable behavior when fetching thousands of records. Can you please provide more information as to why it is behaving this way and how it can be circumvented? Thank you. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2753?page=c... ] Julien Kronegg commented on HHH-2753: ------------------------------------- Workaround for the "not found=ignore" behavior: ----------------------------------------------- You can have @ManyToOne with LAZY loading AND without throwing EntityNotFoundException with the following code: public MyManyToOneEntity getMyManyToOneEntityOrNull() { try { // force fetching the entity (will raise an EntityNotFoundException if not found) getMyManyToOneEntity().toString(); // or whatever method which force a fetch return getMyManyToOneEntity(); } catch (EntityNotFoundException e) { return null; } } This way, Hibernate will issue one query for the main object, and one other query for the MyManyToOneEntity but only when the getMyManyToOneEntityOrNull() method is called. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira