|
From: NHibernate J. <mik...@us...> - 2007-05-07 14:44:05
|
[ http://jira.nhibernate.org/browse/NH-1001?page=all ] Sergey Koshcheyev updated NH-1001: ---------------------------------- Version: (was: 1.2.0.CR2) (was: 1.2.0.CR1) (was: 1.2.0.Beta3) (was: 1.2.0.Beta2) (was: 1.2.0.Beta1) (was: 1.2.0.Alpha1) And what do you want it to do? > Select statement issued for each not-found=ignore > ------------------------------------------------- > > Key: NH-1001 > URL: http://jira.nhibernate.org/browse/NH-1001 > Project: NHibernate > Type: Bug > Components: Core > Versions: 1.2.0.GA > Reporter: Tomer Avissar > Priority: Minor > > When using the not-found=ignore attribute in a one-to-many/many-to-many, NHibernate is issuing a query for every element not found in the collection, even when using an outer join. > In some cases this causes a significant performance overhead. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.nhibernate.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |