All, I have a difficult decision to make and am waffling back and forth. I'm hoping some of you guys might have come across a similar situation and would have some recommendations.
I have a model where a number of entities can by applied only to males or only to females (it's an exercise app). Part of me wants to create sub-entities called "Male…" and "Female…" because EOF will effectively validate relationships for me. Unfortunately, it's a pretty deep entity hierarchy and there would be a lot of entities that would have to fall into this category. Not to mention there are join tables that wouldn't have an M/F flag, but to stay consistent would have to be subclassed as well. Any thoughts? I would do them all with single table inheritance, so there wouldn't be much of a performance hit. Thanks, Ken _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
