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 JAA05892
	for <pgsql-sql@hub.org>; Thu, 12 Aug 1999 09:23:45 -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 JAA17729;
	Thu, 12 Aug 1999 09:23:02 -0400 (EDT)
To: "Mihai Barbos" <barbos@moon.ro>
cc: pgsql-sql@hub.org
Subject: Re: [SQL] UNIQUE constraint 
In-reply-to: Your message of Thu, 12 Aug 1999 08:43:55 +0300
	<002801bee485$af1ab920$4d8823d4@gigell>
Date: Thu, 12 Aug 1999 09:23:02 -0400
Message-ID: <17727.934464182@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

"Mihai Barbos" <barbos@moon.ro> writes:
> Maybe I haven't looked in the roght place but here's my problem:
> I've upgraded to 6.5 and I'm trying to use UNIQUE, something like:
> create table TEST    (
>         testval    something    UNIQUE,
>         .....................,
> );
> In 6.4.2 it worked OK, but now it seems it has no effect. Is there any
> problem with UNIQUE ?

I don't see any:

create table TEST    (
testval    int4 UNIQUE
);
NOTICE:  CREATE TABLE/UNIQUE will create implicit index 'test_testval_key' for table 'test'
CREATE
insert into test values (1);
INSERT 283276 1
insert into test values (1);
ERROR:  Cannot insert a duplicate key into a unique index

You're going to have to be more specific about what problem you
are observing.

			regards, tom lane