"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.
ms
On May 21, 2007, at 3:54 PM, Lachlan Deck wrote:
On 22/05/2007, at 5:34 AM, Mike Schrag wrote:
Looking back, it's not quite as bad as I thought -- It's just that
they chose not to flatten a relationship of the same name, they
copied it. Creature.folderDatas vs Person.folderDatas. This leads
me to question whether it's intentionally not flattened or whether
it's a mistake and should have been flattened.
Actually, that raises a good point. So the relationships ought not
flattened but copied (apart from internalInfo). We see below that
the attributes that they join on are already flattened in the
child... that's why the relationship shouldn't also be flattened
but copied. Okay, that makes sense.
Creature:
{
deleteRule = EODeleteRuleCascade;
destination = FolderData;
internalInfo = {_nameInObjectStore = folderDatas; };
isToMany = Y;
joinSemantic = EOInnerJoin;
joins = ({destinationAttribute = dataId;
sourceAttribute = creatureId; });
name = folderDatas;
ownsDestination = Y;
propagatesPrimaryKey = Y;
},
Person:
{
deleteRule = EODeleteRuleCascade;
destination = FolderData;
isToMany = Y;
joinSemantic = EOInnerJoin;
joins = ({destinationAttribute = dataId;
sourceAttribute = creatureId; });
name = folderDatas;
ownsDestination = Y;
propagatesPrimaryKey = Y;
},
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]
