From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "Zeugswetter Andreas SB SD" <ZeugswetterA(at)spardat(dot)at>, "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp> |
Cc: | <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <pgman(at)candle(dot)pha(dot)pa(dot)us>, <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Roadmap for FE/BE protocol redesign |
Date: | 2003-03-13 19:27:38 |
Message-ID: | 03AF4E498C591348A42FC93DEA9661B8259DA4@mail.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> -----Original Message-----
> From: Zeugswetter Andreas SB SD [mailto:ZeugswetterA(at)spardat(dot)at]
> Sent: 13 March 2003 17:07
> To: Hiroshi Inoue; Dave Page
> Cc: tgl(at)sss(dot)pgh(dot)pa(dot)us; pgman(at)candle(dot)pha(dot)pa(dot)us;
> pgsql-hackers(at)postgresql(dot)org
> Subject: RE: [HACKERS] Roadmap for FE/BE protocol redesign
>
>
> If this where at the protocol level, the client could flag
> what info is wanted, and thus avoid all unwanted overhead.
But the client usually won't know at that point. For example, an ODBC
app executes a query and reads the tuples returned. After that has
occured, the app calls SQLDescribeCol to describe a column in the
resultset...
Regards, Dave.
From | Date | Subject | |
---|---|---|---|
Next Message | Rod Taylor | 2003-03-13 19:32:28 | Re: SQL99 ARRAY support proposal |
Previous Message | Merlin Moncure | 2003-03-13 19:24:45 | Re: Problems with win32 patch/build |