| 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: | Lincoln Yeoh <lyeoh(at)pop(dot)jaring(dot)my>, Justin Clift <justin(at)postgresql(dot)org>, Glen Parker <glenebob(at)nwlink(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Dropping column silently kills multi-coumn index (was |
| Date: | 2003-02-16 01:17:16 |
| Message-ID: | 5302.1045358236@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Tom Lane wrote:
>> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Added to TODO:
> * Disallow DROP COLUMN on a column that is part of a multi-column index
>>
>> That's poorly phrased. What you meant to say is "require CASCADE if ..."
> Actually, no. Does CASCADE make sense in this case?
Yes, it does. The multi-key index is a dependent object, and dropping
dependent objects is exactly what CASCADE is for.
> Do we have precedent
> for CASCADE to remove something that is shared by others?
Certainly. Try dropping a function that is used in several default
expressions, for example.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Doug McNaught | 2003-02-16 01:39:03 | Re: Does postgres have something similiar to the LOAD DATA INFILE |
| Previous Message | Bruce Momjian | 2003-02-16 00:29:35 | Re: Dropping column silently kills multi-coumn index (was |