Re: Vertical Inheritance qualifier based on to many relationship

2011-08-21 Thread David Avendasora
On Aug 21, 2011, at 5:06 PM, Johan Henselmans wrote: > Thanks for all the comments. > > It seems I have to rewrite the first part of my introductory WO-tutorial on > creating a webobjects app, in which I did a vertical inheritance with > subclasses of the contacts. Well... maybe not. Just don

Re: Vertical Inheritance qualifier based on to many relationship

2011-08-21 Thread Johan Henselmans
Thanks for all the comments. It seems I have to rewrite the first part of my introductory WO-tutorial on creating a webobjects app, in which I did a vertical inheritance with subclasses of the contacts. On 21 aug. 2011, at 00:04, David Avendasora wrote: > > On Aug 20, 2011, at 10:43 PM, Ken

Re: Vertical Inheritance qualifier based on to many relationship

2011-08-20 Thread David Avendasora
On Aug 20, 2011, at 10:43 PM, Ken Anderson wrote: > David, > > When you say have a Relationship to the abstract Role class, I'm assuming > you're recommending inheritance here. I do it the exact same way, just > wanted to make sure it's not confusing to say "do abstract this" and also > "get

Re: Vertical Inheritance qualifier based on to many relationship

2011-08-20 Thread Ken Anderson
David, When you say have a Relationship to the abstract Role class, I'm assuming you're recommending inheritance here. I do it the exact same way, just wanted to make sure it's not confusing to say "do abstract this" and also "get rid of inheritance". For me, I have this type of structure in

Re: Vertical Inheritance qualifier based on to many relationship

2011-08-20 Thread David Avendasora
I've been there, Johan. Don't use inheritance. That's what is messing with you. An EO can't switch from being one Class to another. It completely er... um... screws with EOF. Get rid of the inheritance. Just have a Contact class that has a relationship to the abstract Role class, and make all t

Re: Vertical Inheritance qualifier based on to many relationship

2011-08-20 Thread Lachlan Deck
On 20/08/2011, at 6:58 PM, Johan Henselmans wrote: > On 20 aug. 2011, at 01:26, Chuck Hill wrote: > >> On 2011-08-19, at 2:46 PM, Johan Henselmans wrote: > > I thought I used a Role pattern. situation: > base class is contact, others are inheritances all in the same table Sounds like you're con

Re: Vertical Inheritance qualifier based on to many relationship

2011-08-20 Thread Johan Henselmans
On 20 aug. 2011, at 01:26, Chuck Hill wrote:On 2011-08-19, at 2:46 PM, Johan Henselmans wrote:My idea:I have an entity contact, that gets vertically inherited into actor, employee, visitor, nicepersontoalwayinviteforfreetoanyshow, whatever, based on the role somebody/thing plays. A contact can have

Re: Vertical Inheritance qualifier based on to many relationship

2011-08-19 Thread Lachlan Deck
On 20/08/2011, at 9:26 AM, Chuck Hill wrote: > On 2011-08-19, at 2:46 PM, Johan Henselmans wrote: > >> My idea: >> >> I have an entity contact, that gets vertically inherited into actor, >> employee, visitor, nicepersontoalwayinviteforfreetoanyshow, whatever, based >> on the role somebody/thin

Re: Vertical Inheritance qualifier based on to many relationship

2011-08-19 Thread Chuck Hill
On 2011-08-19, at 2:46 PM, Johan Henselmans wrote: > My idea: > > I have an entity contact, that gets vertically inherited into actor, > employee, visitor, nicepersontoalwayinviteforfreetoanyshow, whatever, based > on the role somebody/thing plays. > > A contact can have different roles, whi

Vertical Inheritance qualifier based on to many relationship

2011-08-19 Thread Johan Henselmans
My idea:I have an entity contact, that gets vertically inherited into actor, employee, visitor, nicepersontoalwayinviteforfreetoanyshow, whatever, based on the role somebody/thing plays. A contact can have different roles, which makes this contact playing actor, employee, visitor, nicepersontoalway