Wow. This is great feedback. As for more than two columns.. I don't think I have more than two nullable columns. Often
Ihave a three or four column constraint where only one or two of them are nullable. I've never used constraints or
indexeswith where clauses. I'll have to play with this a bit to understand how it works. Thanks for the tips!
Phill
-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
Sent: Sat 4/29/2006 3:02 PM
To: Bruno Wolff III
Cc: Jeff Frost; Tornroth, Phill; pgsql-sql@postgresql.org
Subject: Re: [SQL] Multi-Column Constraints and Null Values
Bruno Wolff III <bruno@wolff.to> writes:
> To block multiple entries where one of the columns is null he needs to
> add extra checks. One way to do this is to add a partial index for each column
> with the condition that the other column IS NULL. This will cover everything
> but the case where both columns are null. If this case isn't allowed, then
> a row constraint can be used to block it. If it is allowed, the only thing that
> comes to mind is making an SQL function that counts the number of rows where
> both columns are null and calling that function in a row constraint and
> checking that the result is <= 1.
Nah, it's easy:
CREATE UNIQUE INDEX fooi ON foo ((0)) WHERE col1 IS NULL AND col2 IS NULL;
So you'd need a total of four unique indexes (3 of 'em partial) to
enforce the condition for two columns. The real problem with this
is that it doesn't scale well for more than two columns :-(
regards, tom lane