From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | Alban Hertroys <alban(at)magproductions(dot)nl> |
Cc: | Vivek Khera <vivek(at)khera(dot)org>, Postgresql-General General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: NULLs in unique indexes; Was: Oracle purchases Sleepycat |
Date: | 2006-02-16 18:55:33 |
Message-ID: | 43F4CAA5.5010307@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
>
> I still think one shouldn't allow NULL values in unique constraints
> unless it's the _only_ value (any value is unique if there are no other
> values to compare with, after all), but I can't compare myself to
> C.Date, Darwen or Tom Lane... I'm not a database deity :P
You can not declare a unique value on nothing... thus the reasoning :)
>
> I suspect they have some pretty good reasons to treat NULL values in a
> UNIQUE constraint as different even from other NULL values. It sure
> makes me curious though ;)
>
> Regards,
>
--
The PostgreSQL Company - Command Prompt, Inc. 1.503.667.4564
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
Managed Services, Shared and Dedicated Hosting
Co-Authors: plPHP, plPerlNG - http://www.commandprompt.com/
From | Date | Subject | |
---|---|---|---|
Next Message | David Rio Deiros | 2006-02-16 19:06:33 | C trigger using system(3) to execute a php script |
Previous Message | Ken Winter | 2006-02-16 18:48:11 | Re: Does PG really lack a time zone for India? |