Is anyone using:
1) vertical inheritance with a to-one relationship in the parent?
or
2) vertical inheritance two levels deep?
If so, I would love to see the plist files for the parent and child
entities. I'm trying to make Entity Modeler's vertical inheritance
wizard legit, but I personally don't use vertical inheritance at all,
and the EOModeler manual is pretty light on specifics regarding the
actual modeling of them.
If you can't send the actual plists, I'm interested to know:
* Are non-class attributes supposed to be flattened into the
subclass just like class attributes?
* ... non-class relationships?
* Do the flattened attributes need to be the same name as the
attributes from the parent class?
* When you vertically inherit two levels deep ... WTF flattens?
Do you flatten from the top level parent and only new attributes from
each class along the way? Do you (can you even?) flatten the
flattened attributes from your direct parent?
Basically, I just sort of despise vertical inheritance :)
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]
