Skip site navigation (1) Skip section navigation (2)

Re: Roadmap for FE/BE protocol redesign

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
Cc: pgman(at)candle(dot)pha(dot)pa(dot)us, pgsql-hackers(at)postgresql(dot)org,pgsql-interfaces(at)postgresql(dot)org
Subject: Re: Roadmap for FE/BE protocol redesign
Date: 2003-03-11 15:06:07
Message-ID: 4977.1047395167@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-interfaces
"Dave Page" <dpage(at)vale-housing(dot)co(dot)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.

Also, you muttered something about inferring primary keys and number of
relations in query; seems like this feature isn't solving your problem
as far as that goes, because the set of attributes visible in the target
list isn't much help for either.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Oleg BartunovDate: 2003-03-11 15:12:30
Subject: please apply patch to current CVS
Previous:From: Tom LaneDate: 2003-03-11 14:50:25
Subject: Re: [INTERFACES] Roadmap for FE/BE protocol redesign

pgsql-interfaces by date

Next:From: Dave PageDate: 2003-03-11 15:34:34
Subject: Re: Roadmap for FE/BE protocol redesign
Previous:From: Tom LaneDate: 2003-03-11 14:50:25
Subject: Re: [INTERFACES] Roadmap for FE/BE protocol redesign

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group