Databases
StackOverflow2013
Postsdbo
PONHibernate - outer join, not lazy, ignoring not found - how do you build the objects in one statement?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PONHibernate - outer join, not lazy, ignoring not found - how do you build the objects in one statement?
    primarykey
    data
    text
    <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>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USsambomartin
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PONHibernate - outer join, not lazy, ignoring not found - how do you build the objects in one statement?
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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