I am working hard to replace our project's current persistence approach with NHibernate.
I have determined, I think, that the joined-subclass mapping strategy is the way to go given our database design.
I'll attempt to explain my problem with the following example.
I have a PhoneNumber object with the following class hierarchy:
> Item
> CommunicationItem
> PhoneNumber
Our database has corresponding ITEM, COMMUNICATIONITEM, and PHONENUMBER tables.
**The PHONENUMBER table inherits the column values from ITEM & COMMUNICATIONITEM via triggers.
When I load a PhoneNumber entity, the sql that's executed includes joins to ITEM and COMMUNICATIONITEM (as expected).
Since the values from the joined tables are already in the PHONENUMBER table (copied via triggers), is there a way to configure NHibernate to not include the joins to the 2 "inherited" tables?
_________________ jredin
|