Re: Dropping column silently kills multi-coumn index (was

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-15 20:59:07
Message-ID: 25973.1045342747@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:
> 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 ..."

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2003-02-15 21:18:54 Re: Aggregates with non-commutative transition functions
Previous Message Bruce Momjian 2003-02-15 18:29:55 Re: Dropping column silently kills multi-coumn index (was