From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Patches <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: Non-colliding auto generated names |
Date: | 2003-02-18 15:57:56 |
Message-ID: | 23820.1045583876@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> writes:
> If we wanted to stay consistent, then we should be renaming the constraint
> indexes whenever the table is renamed!
I thought about that, too, and I'd be in favor of it if it didn't have
problems of its own. (The big one being that if the new main-table
name is longer or shorter than the old, you would have to redo the
whole derived-name-generation process, or run into possible truncation
problems. So it leads to the same kind of loss of predictability I'm
griping about.)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Paul Ramsey | 2003-02-18 16:06:06 | [Fwd: [postgis-users] Postgis-0.7.4 + PSQL-7.3.1- installation] |
Previous Message | Justin Clift | 2003-02-18 15:25:59 | Re: FW: Changing the default configuration (was Re: |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2003-02-18 17:36:35 | Re: FAQ addition: deleteing all but one unique row |
Previous Message | Tom Lane | 2003-02-18 15:07:36 | Re: pg_avd |