How does PostgreSQL treat null values in unique composite constraints??? - Mailing list pgsql-admin

From P G
Subject How does PostgreSQL treat null values in unique composite constraints???
Date
Msg-id 20030408181332.49933.qmail@web13310.mail.yahoo.com
Whole thread Raw
Responses Re: How does PostgreSQL treat null values in unique composite  (Stephan Szabo <sszabo@megazone23.bigpanda.com>)
Re: How does PostgreSQL treat null values in unique composite  (Michael Brusser <michael@synchronicity.com>)
List pgsql-admin
I have the following table with a unique constraint.

create table testt (
id int,
aa int,
bb int,
constraint pk_testt primary key (id),
constraint cons_testt unique (aa,bb));

Let's say I insert the following:

insert into testt values (1,2,null);
insert into testt values (2,2,null);

I thought this should fail because of the unique
constraint, but it doesn't.  How does PostgreSQL view
the null values in this constraint?  Will someone
explain why I am allowed to make this insertion?

TIA.

__________________________________________________
Do you Yahoo!?
Yahoo! Tax Center - File online, calculators, forms, and more
http://tax.yahoo.com


pgsql-admin by date:

Previous
From: Jeff Boes
Date:
Subject: Re: pg_class.reltuples not reset by VACUUM?
Next
From: Stephan Szabo
Date:
Subject: Re: How does PostgreSQL treat null values in unique composite