Re: [PATCHES] Cascaded Column Drop - Mailing list pgsql-hackers

From Rod Taylor
Subject Re: [PATCHES] Cascaded Column Drop
Date
Msg-id 1033265991.41857.277.camel@jester
Whole thread Raw
In response to Re: [PATCHES] Cascaded Column Drop  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [PATCHES] Cascaded Column Drop  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Sat, 2002-09-28 at 16:38, Tom Lane wrote:
> Rod Taylor <rbt@rbt.ca> writes:
> > Leaving a zero-width table would be best, even if its not so useful.  I
> > don't like rejecting a CASCADE as it kinda defeats the purpose of having
> > CASCADE.
> 
> I did something about this --- as of CVS tip, you can do
> 
> regression=# create table foo (f1 int);
> CREATE TABLE
> regression=# alter table foo drop column f1;
> ALTER TABLE
> regression=# select * from foo;

Which of course would dump as 'create table foo ();'.

I don't think relcache would like a table without any columns, which is
why the above is rejected.


Anyway, should pg_dump ignore the table entirely?  Or do we try to allow
create table () without any attributes?

--  Rod Taylor



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: C vs. C++ contributions
Next
From: Lamar Owen
Date:
Subject: Re: 7.2.3?