Re: Modeling an optional to-one relationship
Re: Modeling an optional to-one relationship
- Subject: Re: Modeling an optional to-one relationship
- From: Chuck Hill <email@hidden>
- Date: Wed, 13 Jan 2010 15:49:52 -0800
Modelling it as FK to PK seems like the way to go, unless I am
misunderstanding what you need.
On Jan 13, 2010, at 3:24 PM, Lon Varscsak wrote:
Yes it is the same PK in both tables but there are no rows in the
relationship. This is a pretty common practice and I just hate
modeling a to-many and then provide interfaces as a to-one.
On Wed, Jan 13, 2010 at 4:14 PM, Travis Britt <email@hidden>
wrote:
Short answer: no. Is the PK not really a PK? If it is a real PK, how
are there rows without it?
On Jan 13, 2010, at 5:53 PM, Lon Varscsak wrote:
> Is there a way to model an optional to-one relationship from the
primary key to a primary key of another object?
_______________________________________________
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
--
Chuck Hill Senior Consultant / VP Development
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
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