Re: Propagate Primary Key Confusion?
Re: Propagate Primary Key Confusion?
- Subject: Re: Propagate Primary Key Confusion?
- From: Chuck Hill <email@hidden>
- Date: Sun, 16 Jan 2005 20:13:48 -0800
Actually, its Owns Destination confusion. :-) Owns Destination means that
the two objects can't exist in isolation. When object A is created, EOF
creates an instance of Object B for you. This happens during
awakeFromInsertion. Very useful in some situations, but not here. For your
purposes, what you want is Delete Rule: Cascade, which you already have.
Chuck
At 09:05 PM 16/01/2005 -0500, Kieran Kelleher wrote:
>I have a account entity with a to-one relationship to ccInformation
>joined on both primary keys.
>
>I have modeled the account.ccInformation relationship as:
>Optionality: Optional
>Delete Rule: Cascade
>Propagate Primary Key checked
>Owns Destination checked
>
>When I create an account EO, a ccInformation EO is AUTOMATICALLY
>created! I don't want this to happen .... it's optional! Is this
>supposed to happen?
>
>So, for "optional to one" is my only choice a foreign key in account
>pointing to ccInformation?
>
>-Kieran
>
> _______________________________________________
>Do not post admin requests to the list. They will be ignored.
>Webobjects-dev mailing list (email@hidden)
>Help/Unsubscribe/Update your Subscription:
e.net
>
>This email sent to email@hidden
>
--
Chuck Hill email@hidden
Global Village Consulting Inc. http://www.global-village.net
_______________________________________________
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