Re: Parallel structure EO modeling
Re: Parallel structure EO modeling
- Subject: Re: Parallel structure EO modeling
- From: Ramsey Gurley <email@hidden>
- Date: Tue, 26 Feb 2013 13:38:41 -0700
Can you give a concrete example illustrating what you mean? Generally I stay away from enforcing business rules with the schema. When business rules change, as they always do, you're boned. I use the schema to enforce data integrity.
Ramsey
On Feb 26, 2013, at 1:11 PM, Ken Anderson wrote:
> 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@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden