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

Re: [PATCHES] Cascaded Column Drop

From: Rod Taylor <rbt(at)rbt(dot)ca>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Tim Knowles <tim(at)ametco(dot)co(dot)uk>,PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCHES] Cascaded Column Drop
Date: 2002-09-29 02:19:50
Message-ID: 1033265991.41857.277.camel@jester (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
On Sat, 2002-09-28 at 16:38, Tom Lane wrote:
> Rod Taylor <rbt(at)rbt(dot)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


In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2002-09-29 02:37:23
Subject: Re: Default privileges for new databases (was Re: Can't import large objects in most recent cvs)
Previous:From: Lamar OwenDate: 2002-09-29 02:19:29
Subject: Re: 7.2.3?

pgsql-patches by date

Next:From: Tom LaneDate: 2002-09-29 02:41:50
Subject: Re: [PATCHES] Cascaded Column Drop
Previous:From: Bruce MomjianDate: 2002-09-29 02:04:49
Subject: Re: 20020822_02_pitr.patch.gz

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