I have the following scenario:
Class License { public CR cr; }
Class abstract CR { public Organization Org; }
class EstOrg : Organization {}
class CompOrg : Organization {......}
Class EstCR : CR { ...}
class CompCR : CR {....}
I'm thinking to use table per concrete class mapping, however with a little
modification as follows:
EstCRs table where it will have EstCR mapped as component and CompCRs table
which will link to CompCRs as a separate db table. Also "Licenses" table
which will link to either EstCRs or CompCRs (ref integrity can't be applied
here).
The reason for this is that i do want to save joins on the db where
necessary. Do you think this is the right approach? Any thoughts how to do
such mapping on fluent NH (although as far as i know FNH doesnt support
table per concrete class).
Thanks
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
