From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
Cc: | "Peter Eisentraut" <peter_e(at)gmx(dot)net>, "PostgreSQL Development" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Creating unique constraints on OID |
Date: | 2001-10-23 02:50:38 |
Message-ID: | 124.1003805438@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> writes:
> So the result of all this is that the behaviour of my ADD UNIQUE code is
> correct in this case?
The AlterTable code wasn't broken; the error was in parser/analyze.c,
which was prematurely rejecting the command.
>> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> Shouldn't this work?
> create table test ( a int, unique (oid) );
> ERROR: CREATE TABLE: column "oid" named in key does not exist
>>
>> Now it does.
> In 7.2 you mean? Or did you just fix it then?
I just fixed it moments before sending that message.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2001-10-23 02:51:53 | LIMIT TODO item |
Previous Message | Bruce Momjian | 2001-10-23 02:38:29 | Re: [HACKERS] To Postgres Devs : Wouldn't changing the selectlimit |