Re: Modeling an optional to-one relationship
Re: Modeling an optional to-one relationship
- Subject: Re: Modeling an optional to-one relationship
- From: Lon Varscsak <email@hidden>
- Date: Wed, 13 Jan 2010 17:07:39 -0700
Sighing is not allowed on the list. ;) I sent an example a few minutes ago. Yes, that does sound like what I'm describing.
On Wed, Jan 13, 2010 at 4:56 PM, Mark Ritchie
<email@hidden> wrote:
On 13/Jan/2010, at 2: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?
*sigh* As with so many conversations theses days... What are you trying to do?
My initial response is look at how the Movies.eomodel is setup for Talent and TalentPhoto.
That's an example where a large blob was broken off from the main table for better storage.
Not strictly 3rd normal form but often done! ;-) Is that similar to the case that you're talking about?
M.
_______________________________________________
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