From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Rod Taylor <rbt(at)rbt(dot)ca>, PostgreSQL Patches <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: Cascaded Column Drop |
Date: | 2002-09-27 04:28:56 |
Message-ID: | 21045.1033100936@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Tom Lane wrote:
>> What I was actually wondering about after reading Tim's report was
>> whether we could support zero-column tables, which would eliminate the
>> need for the special case altogether. I have not looked to see how
>> extensive are the places that assume tuples have > 0 columns ...
> Zero-width tables do sound interesting. Is it somehow non-relational?
Dunno. I wasn't really thinking that zero-width tables are all that
useful by themselves, but it does seem natural that you should be able
to redefine a column by
ALTER TABLE mytab DROP COLUMN foo;
ALTER TABLE mytab ADD COLUMN foo ...;
even if foo is the only column in mytab. Right now we reject that.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tatsuo Ishii | 2002-09-27 04:29:19 | Re: unicode |
Previous Message | Alvaro Herrera | 2002-09-27 04:18:46 | Re: Cascaded Column Drop |
From | Date | Subject | |
---|---|---|---|
Next Message | Rod Taylor | 2002-09-27 04:29:21 | Re: Cascaded Column Drop |
Previous Message | Alvaro Herrera | 2002-09-27 04:18:46 | Re: Cascaded Column Drop |