lay with this a bit to
understand how it works. Thanks for the tips!
Phill
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]
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
>I believe you can add partial unique indexes to cover the case where a
>column is null, but if you have multiple nullable columns you need to
>worry about you end up with a bunch of indexes.
Hmmm. I hadn't thought of that, thanks. Yes, the indexes would be unnessecary
though. Speaking of, shou
eys. I was hoping to find something better, but I
frankly don't have the experience in house to write contstraints I'll have
confidence in.
Thanks for the tip!
Phill
-Original Message-
From: Mikey [mailto:[EMAIL PROTECTED]
Sent: Thu 5/5/2005 12:03 PM
To: Tornroth, Phill
Cc: p
I have many tables who's natural key includes a nullable column. In this cases
it's a soft-delete or 'deprecated' date time. I'd like to add a table
constraint enforcing this constraint without writing a custom procedure, but
I've found that postgres treats NULLs very consistently with respect
