Re: how to implement a foreign key type constraint against a not unique column - Mailing list pgsql-general

From Jasen Betts
Subject Re: how to implement a foreign key type constraint against a not unique column
Date
Msg-id gm31pr$vkk$1@reversiblemaps.ath.cx
Whole thread Raw
In response to how to implement a foreign key type constraint against a not unique column  ("Brent Wood" <b.wood@niwa.co.nz>)
List pgsql-general
On 2009-01-27, Alban Hertroys <dalroi@solfertje.student.utwente.nl> wrote:
> On Jan 25, 2009, at 3:07 AM, Jasen Betts wrote:
>
>>> I want to use this column as a foreign key on a column in another
>>> table
>>> (column 2), but cannot without a full unique index.
>>
>> a full unique index is easy use an expression that's null for -1.
>>
>> create unique index foobar on foo( ( case fee when -1 then null else
>> fee end ) );
>
>
> anything wrong with create unique index foobar on foo where fee <> -1 ?

neither way works for a foreign key.

easiest solution seems to be to insert a record matching -1 in the
other table (with all other fields null)


pgsql-general by date:

Previous
From: Scott Marlowe
Date:
Subject: Re: Indices types, what to use. Btree, Hash, Gin or Gist
Next
From: Jasen Betts
Date:
Subject: Re: Rollback of Query Cancellation