<join> or <one-to-one> perhaps. /Oskar
2009/6/29 Moss <[email protected]>: > > Our database schema has a Payer table with a unique id key named > PayerId. A very few of these payers are special, so we use a primary > key relationship table called DefaultPayer to denote which of those > payers are designated as default payers. DefaultPayer also has > PayerId as its primary key, but DefaultPayer.PayerId has a foreign key > constraint to Payer. However, this is a purely subset relation, not a > subclassing scenario. We really don't want a DefaultPayer entity > class; it hacks up our domain model. Is there a way to tell > NHibernate about the relation without creating another entity? > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
