This is really a single entity split between two tables. This is supported in NHibernate 2.0 via the <join> element. http://ayende.com/Blog/archive/2007/04/24/Multi-Table-Entities-in-NHibernate.aspx
James -- James Kovacs, B.Sc., M.Sc., MCSD, MCT Microsoft MVP - C# Architecture http://www.jameskovacs.com [EMAIL PROTECTED] 403-397-3177 (mobile) On Mon, Sep 29, 2008 at 6:29 AM, James Gregory <[EMAIL PROTECTED]>wrote: > 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 > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
