| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Postgresql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Information Schema and constraint names not unique |
| Date: | 2003-11-07 15:05:20 |
| Message-ID: | 28745.1068217520@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Tom Lane wrote:
>> regression=# create table foo (f1 int check (f1 > 0) check (f1 < 10));
>> ERROR: check constraint "foo_f1" already exists
> Is this a TODO to fix?
Probably should be. I'd be inclined to try to fix it by generating
"foo_f1_1", "foo_f1_2", etc until a non-conflicting name is found.
(Note: the reason it's okay to search for a non-conflicting name in this
context is we only need a lock on the single table in question. It's
no problem anyway in CREATE TABLE, but can still work in ALTER TABLE.)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2003-11-07 15:24:04 | Re: [HACKERS] Changes to Contributor List |
| Previous Message | Andrew Dunstan | 2003-11-07 15:00:18 | Re: Information Schema and constraint names not unique |