I have this model:
interface IMaterialsTest { Sample{get;set;} }
abstract class Sample { ... }
Originally, I was thinking a many-to-one relation made sense but as it
happens I now need to track some info about the relationship between
the sample and materials tests by adding an 'Approved' property, among
other descriptors.
My thought was to invert the relationship to a one-to-many (with
Sample holding the collection) and wrapping the reference to
IMaterialsTest inside an ValueObject called descriptor, but that would
be tough since IMaterialsTest has many implementations.
Would you recommend introducing something like SampleTestDescriptor as
a ValueObject and removing the direct references to the entities in
the object model?
Assuming I don't want a big table called 'MaterialsTest' and use the
joined-subclass strategy in NHib, how else can I model or map
something like this?
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
-~----------~----~----~----~------~----~------~--~---
