Re: Roadmap for FE/BE protocol redesign

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Dave Page <dpage(at)vale-housing(dot)co(dot)uk>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Roadmap for FE/BE protocol redesign
Date: 2003-03-18 06:26:22
Message-ID: 17110.1047968782@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> ... So the application already knows
> that "foo" is the table and "a" is the column. So if the application
> wants to know about details on the column "a", it can execute
> SELECT whatever FROM pg_attribute, pg_class WHERE relname = 'foo' AND attname = 'a';
> With this proposed change, it can replace that with
> SELECT whatever FROM pg_attribute, pg_class WHERE oid = X AND attnum = Y;

Dave will correct me if I'm wrong --- but I think the issue here is that
the client-side library (think ODBC or JDBC) needs to gain this level of
understanding of a query that is presented to it as an SQL-source
string. So no, it doesn't already know that "foo" is the table and "a"
is the column. To find that out, it has to duplicate a lot of backend
code.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Christof Petig 2003-03-18 08:47:36 Re: Roadmap for FE/BE protocol redesign
Previous Message Tom Lane 2003-03-18 06:22:34 Re: XML ouput for psql