• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag
 

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: EOModel needs an easy tweak
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: EOModel needs an easy tweak


  • Subject: Re: EOModel needs an easy tweak
  • From: Steve Peery <email@hidden>
  • Date: Sat, 06 Nov 2010 17:02:52 -0400

If that is the case, then your Abstract Entity Alpha scenario seems reasonable.

Steve

On Nov 6, 2010, at 3:23 PM, Farrukh Ijaz wrote:

> Yes, they will expose certain properties which are symmetrical in all the entities, e.g. title, description, etc.
>
> Consider this requirement as a tree structure which can have nodes that appear to be symmetric but their underlying user object can be different.
>
> Farrukh
>
> Sent from my iPhone
>
> On 2010-11-06, at 9:58 PM, Steve Peery <email@hidden> wrote:
>
>> Is there any shared functionality between Entity A, Entity B, Entity C and Entity D that would justify Abstract Entity Alpha?
>>
>> Steve
>>
>> On Nov 6, 2010, at 7:39 AM, Farrukh Ijaz wrote:
>>
>>> Hi EOF-ologists,
>>>
>>> I've a modelling issue and need to know what could be the suitable fix (or tweak) to fulfil the requirement.
>>>
>>> Below is the existing EO Model.
>>> <Existing.png>
>>> I've two entities (Entity A and Entity B) extending Abstract Entity X but these entities have their own tables (no single table inheritance). I need to design Entity D and Entity E where Entity D has a toMany relationship with Entity E and Entity E needs to have a toOne relationship with Entity A, Entity B, Entity C and Entity D.
>>>
>>> 1. One way can be for Entity E to have four different relationships such as toEntityA, toEntityB, toEntityC and toEntityD. (This is _not_ desirable)
>>> 2. The other way mentioned in the lower diagram where Entity A, Entity B, Entity C and Entity D extend Abstract Entity X and Entity E will have toOne relationship with Abstract Entity X. (This is _desirable_).
>>> <Desired.png>
>>> What would be the easiest way to model such relationship? I'm _not_ relationship expert so may be the way I assumed the model (second diagram) can be wrong or practically impossible?
>>> Also note that I cannot make Entity C and Entity D to extend Abstract Entity X due to some design constraints therefore I think to introduce Abstract Entity Alpha.
>>>
>>> Thanks,
>>>
>>> Farrukh
>>>
>>>
>>>
>>> _______________________________________________
>>> 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

References: 
 >EOModel needs an easy tweak (From: Farrukh Ijaz <email@hidden>)
 >Re: EOModel needs an easy tweak (From: Steve Peery <email@hidden>)
 >Re: EOModel needs an easy tweak (From: Farrukh Ijaz <email@hidden>)

  • Prev by Date: Re: EOModel needs an easy tweak
  • Next by Date: Re: [OT] No more XServe
  • Previous by thread: Re: EOModel needs an easy tweak
  • Next by thread: Re: EOModel needs an easy tweak
  • Index(es):
    • Date
    • Thread