Bryce Nesbitt <[EMAIL PROTECTED]> writes:
> I have a table with the following:
> "eg_vehicle_event_pkey" PRIMARY KEY, btree (event_id)
> "no_duplicate_events" UNIQUE, btree (thing, other_thing,
> "timestamp", number, other_number)
> The "no_duplicate_events" constraint works fine, but if I insert records
> where
> "other_thing" is null, they all go in without complaint. I can insert as
> many duplicates as I want.
This is per SQL spec. You're imagining that two nulls are considered
equal, which they are not.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
