Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id D2261476BFA for ; Fri, 27 Sep 2002 00:13:12 -0400 (EDT) Received: from joeconway.com (unknown [63.210.180.150]) by postgresql.org (Postfix) with ESMTP id 36B7D47632D for ; Fri, 27 Sep 2002 00:13:12 -0400 (EDT) Received: from [192.168.5.3] (account jconway HELO joeconway.com) by joeconway.com (CommuniGate Pro SMTP 3.5.9) with ESMTP-TLS id 1338979; Thu, 26 Sep 2002 20:51:39 -0700 Message-ID: <3D93DA70.5030109@joeconway.com> Date: Thu, 26 Sep 2002 21:11:28 -0700 From: Joe Conway User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Bruce Momjian Cc: Tom Lane , Rod Taylor , PostgreSQL Patches Subject: Re: Cascaded Column Drop References: <200209270400.g8R40l800977@candle.pha.pa.us> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200209/308 X-Sequence-Number: 5510 Bruce Momjian wrote: > 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? > I can see a zero column table as a transition state maybe, but what else would they be useful for? Joe