Actually, this is what the spec defines. You're using match
unspecified, which means:
- If no <match type> was specified then, for each row R1 of the
referencing table, either at least one of the values of the
referencing columns in R1 shall be a null value, or the value of
each referencing column in R1 shall be equal to the value of the
corresponding referenced column in some row of the referenced
table.
Stephan Szabo
sszabo@bigpanda.com
On Sat, 2 Sep 2000, Richard Ellis wrote:
> The submit button on the form located at
> http://www.postgresql.org/bugs/bugs.php?1 results in a report of a
> parsing error, so I'm sending this here as the alternative.
>
> Is the following a bug in the referential integrity system? This is
> for PG 7.0.0. I realize that declaring the "ref" column in t2
> additionally as "not null" would prevent this. However, why does the
> "references" check allow insertion of a null value into t2 when there
> are no corresponding null value in the num column of t1?
>
> If this is actually fixed in 7.0.2, then please accept my apologies.
