On 22/05/2007, at 6:09 AM, Mike Schrag wrote:
"Using EOModeler" Page 74 under Vertical Mapping, step #3:
"Flatten the Person parent entity’s relationships into each child
entity (Employee and Customer)
if it has any relationships, and set them as class properties if
they are class properties in the Person
entity."
So either the manual on how to do it is wrong, or the example of
how to do it is wrong. Awesome.
:-D
My bet's on the manual being wrong.
Thinking about it: it makes absolutely no sense to flatten both the
foreign keys into the child as well as flattening the relationship.
But seeing as EOF requires that you flatten the foreign keys that
leads us (me) to one conclusion: don't flatten relationships into
child - and in fact validate it as wrong to do so please ;-)
Unless anyone can put forward a reasonable argument for why both
would be flattened I'd go ahead and do it.
Well that makes me feel like there's more certainty in this...
with regards,
--
Lachlan Deck
_______________________________________________
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]
