Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2])
	by hub.org (8.9.3/8.9.3) with ESMTP id KAA25131
	for <pgsql-sql@hub.org>; Mon, 23 Aug 1999 10:01:59 -0400 (EDT)
	(envelope-from tgl@sss.pgh.pa.us)
Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id KAA23090;
	Mon, 23 Aug 1999 10:01:08 -0400 (EDT)
To: "Mihai Barbos" <barbos@moon.ro>
cc: pgsql-sql@hub.org
Subject: Re: [SQL] UNIQUE constraint 
In-reply-to: Your message of Sat, 21 Aug 1999 18:01:02 +0300
	<000201beed47$f7dbf140$4a8823d4@gigell>
Date: Mon, 23 Aug 1999 10:01:07 -0400
Message-ID: <23088.935416867@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

"Mihai Barbos" <barbos@moon.ro> writes:
> My fault, the correct situation is
> create table TEST    (
>     testkey    something    PRIMARY KEY,
>     testval    something    UNIQUE,
>          .....................
> );

> PRIMARY KEY works OK, but UNIQUE is ignored.

Oh, OK: that bug was noticed and fixed a couple of weeks ago.  If you
have *both* a PRIMARY KEY and a UNIQUE on a different field, the UNIQUE
gets dropped --- both 6.5 and 6.5.1 have this mistake.  See the patch
Thomas Lockhart posted a week or two back.

			regards, tom lane