From: Chris Bitmead <chrisb@nimrod.itg.telstra.com.au>
To: Mathijs Brands <mathijs@ilse.nl>
Cc: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: chris@bitmead.com, "pgsql-hackers@postgreSQL.org" <pgsql-hackers@postgreSQL.org>
Cc: pgsql-sql@postgreSQL.org
Cc: pgsql-general@postgreSQL.org
Subject: Re: [SQL] Re: [GENERAL] Proposed Changes to PostgreSQL
Date: Thu, 03 Feb 2000 17:29:38 +1100
Message-ID: <38992052.8BA1702E@nimrod.itg.telecom.com.au> (raw)
References: <3898EBCA.2ADFE390@nimrod.itg.telecom.com.au>
<200002030257.VAA00457@candle.pha.pa.us>
<20000203072514.B174@ilse.nl>
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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: chrisb@nimrod.itg.telstra.com.au, mathijs@ilse.nl, pgman@candle.pha.pa.us, pgsql-hackers@postgreSQL.org, pgsql-general@postgreSQL.org
Subject: Re: [SQL] Re: [GENERAL] Proposed Changes to PostgreSQL
In-Reply-To: <38992052.8BA1702E@nimrod.itg.telecom.com.au>
References: <3898EBCA.2ADFE390@nimrod.itg.telecom.com.au> <200002030257.VAA00457@candle.pha.pa.us> <20000203072514.B174@ilse.nl> <38992052.8BA1702E@nimrod.itg.telecom.com.au>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox