Re: TODO: DROP COLUMN .. CASCADE

OK, I will remove the TODO item:
 * Require DROP COLUMN CASCADE for a column that is part of a multi-column index

Can we promote the index drop to a warning if it is multi-column?

---------------------------------------------------------------------------

Rod Taylor wrote:
-- Start of PGP signed section.
> > > Basically I think this proposal would introduce a weird, confusing
> > > dichotomy of behavior between single- and multi-column indexes.
> > > And as Rod pointed out, you'd logically have to do the same for CHECK
> > > constraints depending on whether they mention one or several columns.
> > > (And what of multicolumn foreign keys?)  I see much confusion ahead,
> > > and no payback. 
> > 
> > I do see the confusion argument, but I also see cases where folks are
> > losing the use of an index for single-column lookups.  Others?
> 
> So long as the user has NOTICES enabled, they should see what else was
> dropped along with it. 
> 
> Besides, we should encourage schema modifications to be done in
> transactions, thus they can rollback if they're not happy with the
> results.
> 
> --
> Rod Taylor <rbt@rbt.ca>
> 
> PGP Key: http://www.rbt.ca/rbtpub.asc
-- End of PGP section, PGP failed!

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
359-1001+  If your life is a hard drive,     |  13 Roberts Road +  Christ can be your backup.        |  Newtown Square,
Pennsylvania19073