Re: unique constraint on 2 columns

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jonathan Vanasco <postgres(at)2xlp(dot)com>
Cc: pgsql general <pgsql-general(at)postgresql(dot)org>
Subject: Re: unique constraint on 2 columns
Date: 2007-04-20 21:58:31
Message-ID: 22899.1177106311@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Jonathan Vanasco <postgres(at)2xlp(dot)com> writes:
> Given:
> create table test_a (
> id serial ,
> name_1 varchar(32) ,
> name_2 varchar(32)
> );

> I need name_1 and name_2 to both be unique so that:
> name_1 never appears in name_1 or name_2
> name_2 never appears in name_2 or name_1

I think you should consider redesigning your table layout. Whatever
kluge you come up with to enforce that is not going to be better than
changing the layout. You should put all the names into one unique
column and devise a different representation for whatever the
name_1 vs name_2 relationship is supposed to be.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Jeff Davis 2007-04-20 22:13:33 Re: unique constraint on 2 columns
Previous Message Jonathan Vanasco 2007-04-20 21:56:25 Re: unique constraint on 2 columns