Databases
StackOverflow2013
Postsdbo
PONHibernate Many to One / One to One with differing keys
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PONHibernate Many to One / One to One with differing keys
    primarykey
    data
    text
    <p>Hey all, I'm kicking the tires on NHibernate and have a conoundrum I have been scratching my head over for a bit now, working with a legacy database with some fairly complex relationships.</p> <p>ClaimRoot has a primary key of a claimGUID. ClaimRoot has a bag of Claimdetails associated by claimGUID (this works a treat).</p> <p>The problem is that ClaimRoot also has an optional one to one relationship with ClaimFinancials (not all ClaimRoots have ClaimFinancials, but most do). But the PK for ClaimFinancials is a FormID field. This field exists in the ClaimRoot, but is not the PK.</p> <p>I've posted a mapping below with extra columns removed to protect the innocent.</p> <pre><code> &lt;class name="ClaimRoot" table="tbl_ClaimRoot" schema="DB1.dbo"&gt; &lt;id name="ClaimGUID"&gt; &lt;generator class="guid"/&gt; &lt;/id&gt; &lt;property name="FormID" /&gt; &lt;property name="LastFormNoteText" /&gt; &lt;bag name="ClaimDetails" inverse="true"&gt; &lt;key column="ClaimGUID"/&gt; &lt;one-to-many class="ClaimDetails"/&gt; &lt;/bag&gt; &lt;/class&gt; &lt;class name="ClaimDetails" table="tbl_ClaimDetails" schema="DB2.dbo"&gt; &lt;id name="RowID"&gt; &lt;generator class="native"/&gt; &lt;/id&gt; &lt;property name="ClaimGUID" /&gt; &lt;property name="SeqNo"/&gt; &lt;property name="B1A_InsID" /&gt; &lt;many-to-one name="Root" column="ClaimGUID" foreign-key="ClaimGUID"/&gt; &lt;/class&gt; &lt;class name="ClaimFinancials" table="tbl_ClaimFinancials" schema="DB1.dbo"&gt; &lt;id name="FormID"&gt; &lt;generator class="native"/&gt; &lt;/id&gt; &lt;property name="CreatedDate"/&gt; &lt;property name="SubmittedDate" /&gt; &lt;/class&gt; </code></pre> <p>Thanks in advance! -Bob</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USg .
    1. USBob Palmer
    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 Many to One / One to One with differing keys
      1. This table or related slice is empty.
      1. VTUpMod
    1. COJust a backgrounder FYI - The reason I am pulling these relationships together is that our current POCO has methods who's Sprocs update both the ClaimFinancials and ClaimRoot, or ClaimFinancials and ClaimDetails in a single method call because of the tight relationships, and I'd prefer not to tear apart the legacy app.
      singulars
      1. PONHibernate Many to One / One to One with differing keys
      1. USBob Palmer
 

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