From: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
---|---|
To: | Adrian von Bidder <avbidder(at)fortytwo(dot)ch> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Multicolumn primary key with null value |
Date: | 2010-04-23 08:43:48 |
Message-ID: | 4BD15DC4.7010504@postnewspapers.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 23/04/10 15:50, Adrian von Bidder wrote:
> On Friday 23 April 2010 03.27:29 Craig Ringer wrote:
>> insert into test (a,b) values ('fred',NULL);
>> insert into test (a,b) values ('fred',NULL);
>>
>>
>> ... and will succeed:
>
> Hmm. Perhaps not as ugly as "none" placeholders:
>
> create unique index on test (b) where a is null;
> create unique index on test (a) where b is null;
True ... and Pg can even use them both together for bitmap index scans,
albeit not as efficiently as a single multicolumn index.
This really isn't viable for >2 nullable fields, though, as the number
of indexes increases to impractical levels rather quickly.
--
Craig Ringer
From | Date | Subject | |
---|---|---|---|
Next Message | dipti shah | 2010-04-23 10:31:49 | EXCEPT doesn't compare TIMESTAMP type? |
Previous Message | Adrian von Bidder | 2010-04-23 07:53:55 | Re: Creating indexes? |