Re: Mapping multiple EOs to one table
Re: Mapping multiple EOs to one table
- Subject: Re: Mapping multiple EOs to one table
- From: Chuck Hill <email@hidden>
- Date: Mon, 18 Aug 2003 17:48:41 -0700
They are also unique (must be!) within an inheritance hierarchy based on
the root Entity. Go ahead, try it!
Don't put too much faith in the accuracy of the finer details of those
docs. That's a mid-level overview. There is more that is not documented
than there is.
Chuck
At 11:48 AM 19/08/2003 +1200, Ray Ackland wrote:
>Chuck,
>
>Good point, although possible not applicable. According to P96 of the
>document "Enterprise Objects" it states
>"Objects are uniqued based on their global ID. A global ID
>(com.webobjects.eocontrol.EOGlobalID) is formed from an objects
>primary key and its associated entity".
>
>To me this means that there would be different global IDs for each
>entity and avoid the problem you mention.
>
>Ray.
>
>On Tuesday, Aug 19, 2003, at 11:11 Pacific/Auckland,
>email@hidden wrote:
>
>> When EOF fetches an object it associates the snapshot with the entity
>> type through the EOGlobalID. If you fetch a row from that table
>> containing the same PK then EOF will not change its mind about what
>> class it is. So you could do a fetch for EntityA but get instances of
>> EntityB returned instead. That is why you don't want to do this.
>> Don't treat entities as database views.
>>
>>
>> Chuck
>_______________________________________________
>webobjects-dev mailing list | email@hidden
>Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/webobjects-dev
>Do not post admin requests to the list. They will be ignored.
>
--
Chuck Hill email@hidden
Global Village Consulting Inc. http://www.global-village.net
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.