Thanks for the replies guys. I'm away from the office now but I'll give <join> a try in the morning.
The only thing I would say is that the docs you linked to Fabio aren't very clear that the join element can be used outside of an inheritance situation. I completely overlooked that section when scouring them myself. Thanks again guys! On 9/29/08, Fabio Maulo <[EMAIL PROTECTED]> wrote: > http://www.nhforge.org/doc/nh/en/index.html Chapter 8 > http://knol.google.com/k/fabio-maulo/nhibernate-chapter-8/1nr4enxv3dpeq/11# > > 2008/9/29 James Gregory <[EMAIL PROTECTED]> > >> Hey guys, >> There's a bit of an oddity in our current (legacy) application, in that >> one >> of our entities is actually persisted to two tables. The Brief entity is >> made up from Brief1 and Brief2 tables, and our stored procedure currently >> puts the data in the right table on save. The two tables have a one-to-one >> relationship, in that they both share a primary key value. >> >> Anybody have any recommendations for modelling this with NHibernate? We're >> unable to modify the table structure, and I don't really like the idea of >> having a Brief entity with a one-to-one to Brief2 (even if that's how it >> should be). >> >> Thanks, >> James >> >> > >> > > > -- > 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 -~----------~----~----~----~------~----~------~--~---
