Greg Stark <gsstark@xxxxxxx> writes:
> Tom Lane <tgl@xxxxxxxxxxxxx> writes:
>> Direct your complaints to the ISO SQL standards committee.
> The SQL standard generally treats NULLs as a escape hatch for constraints.
Not for UNIQUE constraints. SQL92 section 4.10 "Integrity constraints":
A unique constraint is satisfied if and only if no two rows in
a table have the same non-null values in the unique columns. In
addition, if the unique constraint was defined with PRIMARY KEY,
then it requires that none of the values in the specified column or
columns be the null value.
The short answer to this thread is that the OP is misusing nulls,
and should pick some non-null value to be his "placeholder".
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
