"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