Re: EOF Inheritance, Relationships between super class and subclass

Sun, 02 Jul 2006 13:41:09 -0700

Mr G. Brown,

I think it would be necessary to understand your object model a little more before being able to recommend if/how to use inheritance.  At the moment, I really don't see any entities you have that are good candidates for inheritance, unless I'm misunderstanding your problem.  It seems to me like you need a Patient entity and a PatientAlias entity, related Patient <->> PatientAlias.

Can you please give us some more detail?

Ken

On Jul 2, 2006, at 1:01 PM, Mr. G Brown wrote:

Hello,

I have a few questions about inheritance, thanks if anybody can help.

The parent class would be a Patient, or more accurately, a PatientAlias, because with typos, name changes (marriage or otherwise) information about the same human being could appear, does appear, under several PatientAliases. 

The derived class would be a VerifiedPatient, which would be like a PatientAlias, but with some more info. 

A VerifiedPatient does have a "to many" relationship to PatientAliases, and a PaitentAlias has a "to one" relationship with a VerifiedPatient.

Now it would be nice to extend a PatientAlias class to a VerifiedPatient class, BUT with the "to many" and "to one" relationships will that work? or will that cause problems? Does EOgenerator work with inheritance?  And what flavor of inheritance would work best here?

Well thanks for your insights.



Mr. G Brown

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:

This email sent to [EMAIL PROTECTED]

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to