Re: constraint -- one or the other column not null - Mailing list pgsql-general

From Dawid Kuroczko
Subject Re: constraint -- one or the other column not null
Date
Msg-id 758d5e7f0609060029x46dc5889g4342d43f84e554ee@mail.gmail.com
Whole thread Raw
In response to constraint -- one or the other column not null  ("George Pavlov" <gpavlov@mynewplace.com>)
Responses Re: constraint -- one or the other column not null  (Ivan Sergio Borgonovo <mail@webthatworks.it>)
List pgsql-general
On 9/6/06, George Pavlov <gpavlov@mynewplace.com> wrote:
> I have two columns, both individually nullable, but a row needs to have
> a value in one or the other. What is the best way to implement the
> constraints? I currently have:
>
> create table f (
>   a int,
>   b int,
>   check (a + b is null),
>   check (coalesce(a,b) is not null)
> );
>
> Is there a better way to do it?

Personally I woud simply put there
   CHECK(a IS NOT NULL OR b IS NOT NULL)
which is probably the simplest form of your constraint. :)

pgsql-general by date:

Previous
From: "George Pavlov"
Date:
Subject: constraint -- one or the other column not null
Next
From: Teodor Sigaev
Date:
Subject: Re: ERROR: Gin doesn't support full scan due to it's awful