|
From: NHibernate J. <nh...@gm...> - 2008-09-30 12:22:34
|
[ http://jira.nhibernate.org/browse/NH-1001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fabio Maulo updated NH-1001:
----------------------------
Fix Version/s: (was: 2.1.0.Alpha1)
> Select statement issued for each not-found=ignore
> -------------------------------------------------
>
> Key: NH-1001
> URL: http://jira.nhibernate.org/browse/NH-1001
> Project: NHibernate
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.2.0.GA
> Reporter: Tomer Avissar
> Priority: Minor
> Attachments: HRNHibernateTest.zip
>
>
> 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
|