Re: PRIMARY KEY on a *group* of columns imply that each - Mailing list pgsql-general

From Scott Marlowe
Subject Re: PRIMARY KEY on a *group* of columns imply that each
Date
Msg-id 1114612616.13303.1285.camel@state.g2switchworks.com
Whole thread Raw
In response to Re: PRIMARY KEY on a *group* of columns imply that each column is NOT  (Stephane Bortzmeyer <bortzmeyer@nic.fr>)
Responses Re: PRIMARY KEY on a *group* of columns imply that each column is NOT  (Stephane Bortzmeyer <bortzmeyer@nic.fr>)
List pgsql-general
On Wed, 2005-04-27 at 09:06, Stephane Bortzmeyer wrote:
> On Wed, Apr 27, 2005 at 05:19:32AM +0000,
>  Patrick TJ McPhee <ptjm@interlog.com> wrote
>  a message of 37 lines which said:
>
> > but you should know that in SQL, unique constraints don't apply to
> > rows containing null values
>
> May be I should but I didn't.
>
> > your table definition will be as you want it, but the constraint you
> > want won't be there.
>
> OK, I will try to write a custom trigger, then.

Often the best bet here, btw, is to declare it not null then use
something other than null to represent null, like the text characters NA
or something.

pgsql-general by date:

Previous
From: Stephane Bortzmeyer
Date:
Subject: Re: PRIMARY KEY on a *group* of columns imply that each column is NOT
Next
From: Sebastian Böck
Date:
Subject: Re: PRIMARY KEY on a *group* of columns imply that each