Re: Modeling optional one-to-one relationships correctly

2007-01-11 Thread Robert Walker
And I suppose there is no way to "propagate" for example the primary key of B into A.bFid when you setBrelationship(A) ? Yes this is correct. Primary key propagation can only happen in one direction, by definition. You either propagate from A to B or B to A. Example: 1. EOF generates 5 f

Re: Modeling optional one-to-one relationships correctly

2007-01-11 Thread Fabrice Pipart
On Jan 11, 2007, at 4:20 PM, Robert Walker wrote: Fabrice, The problem that you are having is related to primary key generation. There is no way for EOF to guarantee the generation of the same primary key values to two different entities. This is why modeling one-to-one relationships i

Re: Modeling optional one-to-one relationships correctly

2007-01-11 Thread Robert Walker
Fabrice, The problem that you are having is related to primary key generation. There is no way for EOF to guarantee the generation of the same primary key values to two different entities. This is why modeling one-to-one relationships in EOF normally uses primary key propagation. What

Modeling optional one-to-one relationships correctly

2007-01-11 Thread Fabrice Pipart
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, destinati