Propagate Primary Key Confusion?
Propagate Primary Key Confusion?
- Subject: Propagate Primary Key Confusion?
- From: Kieran Kelleher <email@hidden>
- Date: Sun, 16 Jan 2005 21:05:14 -0500
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:
This email sent to email@hidden