| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Setting a pre-existing index as a primary key |
| Date: | 2008-05-10 15:32:34 |
| Message-ID: | 4825C012.4000803@commandprompt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
>> Well it should be optional but it would be nice if we had the option to
>> have it renamed per the default... meaning the same output if I were to
>> do this:
>
> If you want that, you can rename the index (either before or afterwards).
> I don't see any reason to clutter the make-constraint-from-index command
> with questions of renaming.
As a counter point, I don't see any reason to make the DBA's life
harder. Sure it is just one step but it is a human step, prone to error
and taking more time than it should. Why not just make it easy?
Especially when the easy isn't sacrificing data integrity or quality of
product?
Sincerely,
Joshua D. Drake
>
> regards, tom lane
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2008-05-10 15:55:17 | Re: Setting a pre-existing index as a primary key |
| Previous Message | Tom Lane | 2008-05-10 15:10:37 | Re: Setting a pre-existing index as a primary key |