From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Rod Taylor <rbt(at)rbt(dot)ca> |
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:41:50 |
Message-ID: | 7168.1033267310@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Rod Taylor <rbt(at)rbt(dot)ca> writes:
>> 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 ();'.
True. I didn't say that everything would be happy with it ;-). I think
that a zero-column table is only useful as a transient state, and so I'm
happy as long as the backend doesn't core dump.
> I don't think relcache would like a table without any columns, which is
> why the above is rejected.
Relcache doesn't seem to have a problem with it.
> Anyway, should pg_dump ignore the table entirely? Or do we try to allow
> create table () without any attributes?
I feel no strong need to do either. But it likely would only take
removal of this error check:
regression=# create table foo ();
ERROR: DefineRelation: please inherit from a relation or define an attribute
at least as far as the backend goes.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2002-09-29 02:47:42 | Re: Default privileges for new databases (was Re: Can't import |
Previous Message | Tom Lane | 2002-09-29 02:37:23 | Re: Default privileges for new databases (was Re: Can't import large objects in most recent cvs) |
From | Date | Subject | |
---|---|---|---|
Next Message | Rod Taylor | 2002-09-29 02:50:32 | Re: [PATCHES] Cascaded Column Drop |
Previous Message | Rod Taylor | 2002-09-29 02:19:50 | Re: [PATCHES] Cascaded Column Drop |