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

Re: TODO: DROP COLUMN .. CASCADE

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Rod Taylor <rbt(at)rbt(dot)ca>,PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: TODO: DROP COLUMN .. CASCADE
Date: 2003-03-06 17:15:50
Message-ID: 200303061715.h26HFoR06738@candle.pha.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Tom Lane wrote:
> Rod Taylor <rbt(at)rbt(dot)ca> writes:
> > Require DROP COLUMN CASCADE for a column that is part of a multi-column
> > index
> 
> > Do we want the same behaviour for PRIMARY KEY(col1, col2)? CHECK(col1 >
> > col2)? etc. as well?
> 
> Personally I'm not sold on the sensefulness of the TODO item to begin
> with.

The current code just drops any index that inludes the dropped column,
even if the column is the second column in a multi-column index.  Does
that seem OK to you?

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

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2003-03-06 17:25:48
Subject: Re: TODO: DROP COLUMN .. CASCADE
Previous:From: Tom LaneDate: 2003-03-06 17:05:48
Subject: Re: Row level stats

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