btw... If you have two properties of the same type (both pointing the same table) the relation is not a one-to-one.
P.S. perhaps with "null row" you mean "null value in a column" On Fri, Feb 4, 2011 at 2:13 PM, Fabio Maulo <[email protected]> wrote: > Those relations are mapped as many-to-one. > Here some mapping-pattern for one-to-one > http://fabiomaulo.blogspot.com/2010/03/conform-mapping-one-to-one.html > > > On Fri, Feb 4, 2011 at 8:01 AM, Peter Forstmeier < > [email protected]> wrote: > >> Hi, >> i have One-To-One Relations from Project To Address as shown in the >> mappings: >> >> References(x => >> x.ProjectAddress).Not.LazyLoad().Cascade.SaveUpdate(); >> References(x => x.Architekt).Not.LazyLoad().Cascade.SaveUpdate(); >> >> Both references can be null per definition and references the same >> Table(i use AddressTable for all Addresses in my DB) >> >> So, if any of the Addresses in Project is null, NHibernate inserts a >> 'Null' Row in the AddressTable. >> Is this the correct behavior or did i miss something. >> Any help, also in restructuring the mepping is welcome. >> >> Peter >> >> -- >> You received this message because you are subscribed to the Google Groups >> "nhusers" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]<nhusers%[email protected]> >> . >> For more options, visit this group at >> http://groups.google.com/group/nhusers?hl=en. >> >> > > > -- > Fabio Maulo > > -- Fabio Maulo -- You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
