Received: from serv0.ilse.net (serv0.ilse.nl [194.158.182.236]) by hub.org (8.9.3/8.9.3) with ESMTP id BAA97909; Thu, 3 Feb 2000 01:26:46 -0500 (EST) (envelope-from mathijs@ilse.nl) Received: (from mathijs@localhost) by serv0.ilse.net (8.8.8/8.6.12) id HAA00438; Thu, 3 Feb 2000 07:25:15 +0100 (MET) Date: Thu, 3 Feb 2000 07:25:15 +0100 From: Mathijs Brands To: Bruce Momjian Cc: chris@bitmead.com, "pgsql-hackers@postgreSQL.org" , pgsql-sql@postgreSQL.org, pgsql-general@postgreSQL.org Subject: Re: [SQL] Re: [GENERAL] Proposed Changes to PostgreSQL Message-ID: <20000203072514.B174@ilse.nl> References: <3898EBCA.2ADFE390@nimrod.itg.telecom.com.au> <200002030257.VAA00457@candle.pha.pa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200002030257.VAA00457@candle.pha.pa.us>; from pgman@candle.pha.pa.us on Wed, Feb 02, 2000 at 09:57:48PM -0500 X-Unexpected-Header: The Spanish Inquisition 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. Mathijs