Modeling optional one-to-one relationships correctly
Modeling optional one-to-one relationships correctly
- Subject: Modeling optional one-to-one relationships correctly
- From: Fabrice Pipart <email@hidden>
- Date: Thu, 11 Jan 2007 10:50:28 +0100
| Hi all !
I recently modeled my first one-to-one relationship in my EOModel (please dont laugh). And of course I had troubles ;-) I want this relationship to be optional and to be both sided. Here is how I did it :
Entity A idA bFid bRelationship (source bFid, destination idB)
Entity B idB aFid aRelationship (source aFid, destination idA)
I want both relationships to be optional. There is no propagate primary key since I don't really understand how it works.
The problem is : if I set A in B, I do have aFid set in DB but I don't have bFid set :-(
I tried to understand the mechanisms of optional one-to-one relationships in the mailing list archives but I could not figure it out. Could someone please summarize what is a good way to model it?
Regards
Fabrice
www.easyshadow.com
International Corporate Consulting Palais de la Scala 1 avenue Henri Dunant Suite 1155 MC - 98000 Monaco
Skype: fabrice.pipart Tel. +377 97 98 21 04 (direct) Fax. +377 97 70 88 07
|
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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