|
From: NHibernate J. <mik...@us...> - 2007-06-10 12:59:40
|
[ http://jira.nhibernate.org/browse/NH-1001?page=3Dall ] Tomer Avissar updated NH-1001: ------------------------------ Attachment: HRNHibernateTest.zip This test case is against the Oracle "HR" schema, the file db.xls displays = the relevant rows (I tried to create the test case on the xsl directly, but= apparently excel doesn=E2=80=99t support join).=20 The case is demonstrated in the Form1_Load method. the "sql generated.txt" file (in the zip) contains the sql generated, taken= from the VS output window. > Select statement issued for each not-found=3Dignore > ------------------------------------------------- > > 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 > Attachments: HRNHibernateTest.zip > > When using the not-found=3Dignore attribute in a one-to-many/many-to-many= , NHibernate is issuing a query for every element not found in the collecti= on, even when using an outer join.=20 > In some cases this causes a significant performance overhead. --=20 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 |