From: | "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net> |
---|---|
To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Is this a bug? |
Date: | 2005-01-25 17:43:16 |
Message-ID: | 41F68534.4070806@zeut.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
I think this may have been discussed before but I found this a bit
surprising:
foo=# SELECT version();
version
---------------------------------------------------------------------------------------------------------
PostgreSQL 7.4.3 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 3.3.2
20031022 (Red Hat Linux 3.3.2-1)
(1 row)
foo=# create table foo (id1 int, id2 int, id3 int);
CREATE TABLE
foo=# ALTER TABLE foo ADD unique (id1,id2);
NOTICE: ALTER TABLE / ADD UNIQUE will create implicit index
"foo_id1_key" for table "foo"
ALTER TABLE
foo=# ALTER TABLE foo ADD unique (id1,id3);
NOTICE: ALTER TABLE / ADD UNIQUE will create implicit index
"foo_id1_key" for table "foo"
ERROR: relation "foo_id1_key" already exists
foo=#
Now, I know I can specify a constraint name inside the alter command,
but I still expected this to work.
Thanks,
Matthew
From | Date | Subject | |
---|---|---|---|
Next Message | Matthew T. O'Connor | 2005-01-25 17:44:04 | Re: Goals for 8.1 |
Previous Message | Marc G. Fournier | 2005-01-25 17:39:04 | Re: Goals for 8.1 |