From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Terrence Brannon <metaperl@mac.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: how could a foreign key ever be NULL?
Date: Mon, 17 Dec 2001 12:06:10 -0500 (EST)
Message-ID: <200112171706.fBHH6Bh06057@candle.pha.pa.us> (raw)
In-Reply-To: <8BBB36A0-F2E2-11D5-92F7-003065C2A10C@mac.com>
> The Momjian book states:
>
> A single-column foreign key is either NULL or matches a primary key
>
> But the problem I have with this statement is that a primary key
> cannot be null or duplicate. And since the foreign key references
> a value that is neither null or duplicate, how could it ever be
> NULL?
Uh, you could have a foreign key row that doesn't match a primary key
row, and is hence NULL, can't you?
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: pgman@candle.pha.pa.us, metaperl@mac.com
Subject: Re: how could a foreign key ever be NULL?
In-Reply-To: <200112171706.fBHH6Bh06057@candle.pha.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox