From: Kevin Brown <kevin@sysexperts.com>
To: pgsql-hackers@postgresql.org
Subject: Re: Roadmap for FE/BE protocol redesign
Date: Tue, 11 Mar 2003 14:55:23 -0800
Message-ID: <20030311225523.GB1833@filer> (raw)
In-Reply-To: <4977.1047395167@sss.pgh.pa.us>
References: <1942.1047350265@sss.pgh.pa.us>
<200303110244.h2B2i1j15763@candle.pha.pa.us>
<50149.80.177.99.193.1047375273.squirrel@ssl.vale-housing.co.uk>
<4977.1047395167@sss.pgh.pa.us>
Tom Lane wrote:
> "Dave Page" <dpage@vale-housing.co.uk> writes:
> > Well, what would constitute a complete spec? I think I've told the group
> > what I would like to be able to do, what unanswered questions can I
> > (hopefully :-) ) answer?
>
> I'm still unclear on exactly what your needs are. In the first place,
> are you expecting to obtain data from arbitrary SELECT statements, or
> only from statements of the form "SELECT * FROM single_table"? You've
> also been confusing as to whether you want transparency of views (ie,
> does a select from a view return data about the view's nominal columns
> or about the underlying base table columns?). What about cases
> involving aggregates or grouping --- there may be simple Vars in the
> target list, but they can hardly be thought to represent updatable values.
These questions can't possibly be unique to PG -- other database
vendors must have answered these questions for their implementations
of ODBC/JDBC too, or their databases would give ODBC and JDBC client
authors the same kinds of trouble.
So ... how have these questions been answered by other database
vendors?
The spec may be underspecified on these points, but since the entire
purpose of ODBC and JDBC is to provide a database-independent
framework for application authors to use, it follows that
compatibility with other implementations is highly desirable. So
doing more or less what other database vendors have done in response
to these underspecified issues is probably a sensible course of action
when there's no other obviously better answer.
--
Kevin Brown kevin@sysexperts.com
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 using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: kevin@sysexperts.com, pgsql-hackers@postgresql.org
Subject: Re: Roadmap for FE/BE protocol redesign
In-Reply-To: <20030311225523.GB1833@filer>
* 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