Re: Dropping column silently kills multi-coumn index (was [ODBC] Error when accessing tables with deleted columns)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Glen Parker" <glenebob(at)nwlink(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Dropping column silently kills multi-coumn index (was [ODBC] Error when accessing tables with deleted columns)
Date: 2003-01-29 23:33:01
Message-ID: 5299.1043883181@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-odbc

"Glen Parker" <glenebob(at)nwlink(dot)com> writes:
> Note that the ALTER TABLE query succeeded *quietly* and did in fact drop
> the index.

If indexes require a CASCADE to be dropped by DROP COLUMN, then DROP
TABLE on an indexed table would also require CASCADE. Does that seem
like a good idea?

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Robert Treat 2003-01-29 23:46:38 Re: Website troubles
Previous Message Patrick Hatcher 2003-01-29 23:30:36 COPY..FROM question on 7.3

Browse pgsql-odbc by date

  From Date Subject
Next Message Dave Page 2003-01-29 23:35:20 Re: Error when accessing tables with deleted columns
Previous Message Glen Parker 2003-01-29 22:47:04 Dropping column silently kills multi-coumn index (was [ODBC] Error when accessing tables with deleted columns)