Maybe I should take a step back. I assumed I wanted inheritance
at all because I have a basic EO called Person in a model in a
utility framework, and in a particular app I want to add three
relationships to app-specific EOs. (In other apps, Person might
be sufficient as it is, and I would instantiate it as an EO.) Is
this an example of where one would use inheritance? Is HI a bad
choice, and should I use STI instead?
I'd probably use HI in this case. I might also just dynamically add
the relationships when the models are loaded. HI is less tricky.
I use Partial Entities in Project Wonder for this, but they are still
sort of experimental.
ms
_______________________________________________
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]
