Received: from mailo.vtcif.telstra.com.au (mailo.vtcif.telstra.com.au [202.12.144.17]) by hub.org (8.9.3/8.9.3) with ESMTP id BAA02402; Thu, 3 Feb 2000 01:34:29 -0500 (EST) (envelope-from chrisb@nimrod.itg.telstra.com.au) Received: (from uucp@localhost) by mailo.vtcif.telstra.com.au (8.8.2/8.6.9) id RAA15981; Thu, 3 Feb 2000 17:33:55 +1100 (EST) Received: from maili.vtcif.telstra.com.au(202.12.142.17) via SMTP by mailo.vtcif.telstra.com.au, id smtpdl0uvl_; Thu Feb 3 17:33:11 2000 Received: (from uucp@localhost) by maili.vtcif.telstra.com.au (8.8.2/8.6.9) id RAA14061; Thu, 3 Feb 2000 17:33:09 +1100 (EST) Received: from localhost(127.0.0.1), claiming to be "mail.cdn.telstra.com.au" via SMTP by localhost, id smtpdxGA1._; Thu Feb 3 17:31:12 2000 Received: from lunitari.nimrod.itg.telecom.com.au (lunitari.nimrod.itg.telecom.com.au [192.53.254.48]) by mail.cdn.telstra.com.au (8.8.2/8.6.9) with ESMTP id RAA20762; Thu, 3 Feb 2000 17:31:11 +1100 (EST) Received: from nimrod.itg.telecom.com.au (majere [192.53.254.45]) by lunitari.nimrod.itg.telecom.com.au (8.9.1/8.9.3) with ESMTP id RAA16195; Thu, 3 Feb 2000 17:30:26 +1100 (EST) Sender: chrisb@nimrod.itg.telstra.com.au Message-ID: <38992052.8BA1702E@nimrod.itg.telecom.com.au> Date: Thu, 03 Feb 2000 17:29:38 +1100 From: Chris Bitmead Reply-To: chris@bitmead.com Organization: IBM Global Services X-Mailer: Mozilla 4.6 [en] (X11; I; SunOS 5.6 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: Mathijs Brands CC: Bruce Momjian , chris@bitmead.com, "pgsql-hackers@postgreSQL.org" , pgsql-sql@postgreSQL.org, pgsql-general@postgreSQL.org Subject: Re: [SQL] Re: [GENERAL] Proposed Changes to PostgreSQL References: <3898EBCA.2ADFE390@nimrod.itg.telecom.com.au> <200002030257.VAA00457@candle.pha.pa.us> <20000203072514.B174@ilse.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mathijs Brands wrote: > > On Wed, Feb 02, 2000 at 09:57:48PM -0500, Bruce Momjian allegedly wrote: > > > > > 3) The ability to return different types of rows from a SELECT. This > > > > > is to allow implementation of ODBMS functionality where a query could > > > > > be required to instantiate objects of differing types with differing > > > > > attributes. > > > > > > > > This bothers me. We return relational data, showing the same number of > > > > columns and types for every query. I don't think we want to change > > > > that, even for OO. > > > > > > What aspects bother you? This is the fundamental important thing about > > > object databases. > > > > I fear it is totally against the way our API works. How does someone > > see how many columns in the returned row? > > This would probably break applications written in PHP and Perl (and > possibly others) that have their queryresults returned to them in a > numerically indexed array (index by offset). If this behaviour could > be turned off, than it shouldn't be a problem. It wouldn't affect them because the current APIs would continue to return the same base-level columns. You would only get access to the extra columns with a new API.