You seem to have a problem with the definition of your entites.
Can you do a simple diagram of how you see your domain?
Maybe it's just a miscommunication. What I can tell you is, this is NOT a
complex model at all, NOR will you have to jump through any hoops... as long
as you get the model right.
The name change was because you said "a contact might not be a client".
Fine, so the superclass is not "Client". But what makes a "Client" different
from a Contact/Company?
Diego
On Wed, Aug 11, 2010 at 13:53, Blaise <[email protected]> wrote:
> > How about changing the name "Client" to "BusinessPartner"?
> > Then, the "Client" property of your Invoice class is a BusinessPartner.
>
> Not following you. How does changing the name of an entity solve
> anything ?
>
> Frans' conclusion is pretty much the one I was afraid of earing
> - either try to jumps through unnatural hoops, which I don't like
> - or just duplicate the data (John Doe the friend and John Dow the
> business partner), which I don't like either.
>
> --
> 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]<nhusers%[email protected]>
> .
> For more options, visit this group at
> http://groups.google.com/group/nhusers?hl=en.
>
>
--
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.
