StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PONHibernate - outer join, not lazy, ignoring not found - how do you build the objects in one statement?
text
Body
copied!<p>I've read many posts about this, the last being a statement saying the behaviour i'm experiencing the the expected if not preferred way.</p> <p>I've got a handful of domain models mapped to their database tables.</p> <p>I'm using a Criteria object to query them.</p> <pre><code> var query = session.CreateCriteria(typeof(Posting)) .CreateAlias("Person", "person", JoinType.InnerJoin).SetFetchMode("Person", FetchMode.Eager) .CreateAlias("Location", "location", JoinType.InnerJoin).SetFetchMode("Location", FetchMode.Eager) .CreateAlias("Post", "post", JoinType.InnerJoin).SetFetchMode("Post", FetchMode.Eager) .CreateAlias("post.Zone", "postzone", JoinType.LeftOuterJoin).SetFetchMode("post.Zone", FetchMode.Select) </code></pre> <p>It produces the exact statment I'm looking for. I'd expect it to populate the objects eagerly (which it does) and leave nulls for post.Zone where the relationship fails.</p> <p>In my mapping i've had to say not-found=ignore (Notfound.Ignore() FNH) which due to the outer join is causing NH to generate a number of sub-query - all on the Zone table - which doesn't seem necessary to me, especially as it already had the data it need to populate the Zone object.</p> <p>Can anyone she any light on any changes I can make to the Mapping or Query/Criteria to keep this load to a single query, or should I expect an extra statement for every record outer joined to?</p> <p>Thanks, Sam</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload