On Sep 22, 2008, at 13:07, Chuck Hill wrote:
Yeah, sounds like this might end up kicking me in the ass.
Especially since I can't override client side class descriptions,
so I would have a discrepancy between what EOs and class
descriptions see as inverse relationships. Not sure I like this
idea, it might have unforeseeable consequences, no? More work...
Does that method exist for client side EOs?
Yep, it does. I am just afraid of meddling with it... Especially
since EOs go through a different life-cycle in a JC situation, there
are more variables to control (server side EOs, server side class
descriptions, client side EOs, client side CDs and all the EOF in
between).
But, to come back on the original idea, what do you think of
putting a uniqueness constraint on the FK? ould that somewhere
somehow screw the object graph up beyond repair?
I can't see how it would harm it. If violated, the save will fail.
Thanks, seems worth trying out.
F
_______________________________________________
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]
