From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: chris@bitmead.com, "pgsql-hackers@postgreSQL.org" <pgsql-hackers@postgresql.org>
Subject: Re: [HACKERS] Re: [SQL] Re: [GENERAL] Proposed Changes to PostgreSQL
Date: Wed, 2 Feb 2000 22:58:41 -0500 (EST)
Message-ID: <200002030358.WAA03721@candle.pha.pa.us> (raw)
In-Reply-To: <24816.949549188@sss.pgh.pa.us>
> Yeah. In fact, since the field is not required except on specific
> user request (explicit SELECT, or if you like Chris' SET SHOW_CLASSNAME
> idea, that'd still get translated into a SELECT target item at some
> pretty early stage), I don't see any need for it to get added to the
> HeapTupleHeader fields. That makes the implementation a *lot* cleaner
> because you wouldn't need in-memory HeapTupleHeader to be different from
> on-disk headers. I'm visualizing this as a parameterless function (or
> maybe a new primitive expression node type) that gets evaluated during
> ExecProject's construction of the output tuple for a a bottom-level
> seqscan or indexscan plan node. The only trick is to persuade the
> planner to push it down to the bottom level; normally anything that
> isn't a Var gets evaluated at the top of the plan tree.
Yes, I agree this is a good way to do it.
> >>>> 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.
>
> My thought also. If we had a *real* object orientation, then a returned
> column would have an abstract data type that might correspond to an
> object supertype. Of course that just pushes the problem down a level:
> how does the application know what methods the returned object has?
> How can it even invoke those methods --- whatever code might exist
> for them would live on the server, presumably, not get shipped around
> in query results.
Agreed.
--
Bruce Momjian | http://www.op.net/~candle
pgman@candle.pha.pa.us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
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: pgman@candle.pha.pa.us, tgl@sss.pgh.pa.us, pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] Re: [SQL] Re: [GENERAL] Proposed Changes to PostgreSQL
In-Reply-To: <200002030358.WAA03721@candle.pha.pa.us>
References: <24816.949549188@sss.pgh.pa.us> <200002030358.WAA03721@candle.pha.pa.us>
* 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