Re: BUG #2975: UNIQUE INDEX doesn't work - Mailing list pgsql-bugs

From Michael Fuhr
Subject Re: BUG #2975: UNIQUE INDEX doesn't work
Date
Msg-id 20070214144809.GA16753@winnie.fuhr.org
Whole thread Raw
In response to BUG #2975: UNIQUE INDEX doesn't work  ("Steven" <s.lambert@madeware.nl>)
List pgsql-bugs
On Wed, Feb 14, 2007 at 10:01:58AM +0100, Steven Lambert wrote:
> You are right, the index has more columns and one of them have most of the
> time the value NULL.
> It is the date when the record has been "deleted"

See "Unique Constraints" in the documentation, in particular the
last paragraph:

http://www.postgresql.org/docs/8.1/interactive/ddl-constraints.html#AEN2016

"However, null values are not considered equal in this comparison.
That means even in the presence of a unique constraint it is possible
to store duplicate rows that contain a null value in at least one
of the constrained columns."

This has been discussed before; search the archives for words like
"null", "unique", and "comparison" or "compare".

--
Michael Fuhr

pgsql-bugs by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: BUG #2998: Installation Failed due to Permissions
Next
From: Bruce Momjian
Date:
Subject: Re: BUG #2997: parse error: setObject("2004-August-15",java.sql.Types.DATE)