Skip site navigation (1) Skip section navigation (2)

Re: TODO: DROP COLUMN .. CASCADE

From: Rod Taylor <rbt(at)rbt(dot)ca>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>,PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: TODO: DROP COLUMN .. CASCADE
Date: 2003-03-06 18:13:28
Message-ID: 1046974408.487.49.camel@jester (view raw or flat)
Thread:
Lists: pgsql-hackers
> > 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(at)rbt(dot)ca>

PGP Key: http://www.rbt.ca/rbtpub.asc

In response to

Responses

pgsql-hackers by date

Next:From: Antti HaapalaDate: 2003-03-06 18:30:57
Subject: Re: TODO: DROP COLUMN .. CASCADE
Previous:From: Tom LaneDate: 2003-03-06 18:12:35
Subject: Re: Partial index on date column

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group