i think you have it really. the three tables could share one association table.
but how do you map that in nhibernate? On Aug 28, 5:21 pm, William Chang <[email protected]> wrote: > I'm having trouble picturing what you saying... > > One way is have those three tables to be part of one association table > (EmployeesDependentsPlans). > > Second way is to have your association table, EmployeePlan, have a > primary key. Thus, you can create another association table with > Dependents. > > Again, I'm having trouble picturing what you saying. > > Sincerely, > William Chang > > On Aug 28, 5:33 pm, Ralph Balck <[email protected]> wrote: > > > I have a many-to-many relationship between an Employee and a Plan. > > The cross table is called EmployeePlan. > > > This was all well and fine until we added Dependents into the mix. > > Each Employee has many Dependents. The tricky part is that each > > Dependent can be associated with any or all of the Plans that the > > employee has. So basically, there is a many to many between Employee > > and Plan, and there is a many to many between Dependents and the > > *cross table* EmployeePlan. > > > How do i map this? is there a better way than a many-to-many to a > > many-to-many? > > > thanks! > > Ralph > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
