Re: Getting the results columns before execution

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Shachar Shemesh <psql(at)shemesh(dot)biz>, Hackers <pgsql-hackers(at)postgresql(dot)org>, PostgreSQL OLE DB development <oledb-dev(at)gborg(dot)postgresql(dot)org>
Subject: Re: Getting the results columns before execution
Date: 2004-01-25 20:55:23
Message-ID: 28390.1075064123@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Tom Lane wrote:
>>> Are those exposed through the libpq interface?
>>
>> No, because libpq doesn't really have any concept of prepared statements.
>> It would probably make sense to add some more API to libpq to allow
>> creation and interrogation of prepared statements, but no one's got
>> around to that yet.

> Uh, if libpq doesn't know about it, how is that information accessed?

That's exactly the problem...

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message elein 2004-01-25 21:43:25 Re: Named arguments in function calls
Previous Message Tom Lane 2004-01-25 19:54:12 Re: Named arguments in function calls