Re: One to One Relationship

Hi,
you have two tables t1 and t2.
t1 is master table with PK and t2 is detail table with FK. create an unique constraint on t2 FK field.

best regards

wizofoz2k_at_yahoo.com.au (Nuno Souto) wrote in message news:<73e20c6c.0303171943.401ace74_at_posting.google.com>...
> Karsten Farrell <kfarrell_at_belgariad.com> wrote in message news:<MPG.18dffcb3604e242d989700_at_news.la.sbcglobal.net>...
> > >
> > >
> > While I agree that a 1:1 relationship should be a rare occurance, there
> > are some valid reasons for implementing this relationship. A few reasons
> > I can think of off the top of my head:
> >snip
>
>
> Bingo! While a pure 1:1 relationship is a simple relational table,
> an OPTIONAL 1:1 relationship can indeed (mostly for optimal storage
> reasons!) be stored in more than one table.
> I've got a feeling the original poster didn't intend it that way,
> but indeed it can happen.
>
>
> > There are probably other reasons. You have to look at your business
>
> Yes, but you just about covered the most important ones!
>
> Cheers
> Nuno Souto
> wizofoz2k_at_yahoo.com.au.nospam
Received on Wed Mar 19 2003 - 06:08:12 CST