| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Mihai Barbos" <barbos(at)moon(dot)ro> |
| Cc: | pgsql-sql(at)hub(dot)org |
| Subject: | Re: [SQL] UNIQUE constraint |
| Date: | 1999-08-23 14:01:07 |
| Message-ID: | 23088.935416867@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
"Mihai Barbos" <barbos(at)moon(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | José Soares | 1999-08-23 14:02:38 | Re: [HACKERS] RE: [SQL] datediff function |
| Previous Message | Albert REINER | 1999-08-23 13:42:30 | Expression with aggregate |