From: | Jan Wieck <JanWieck(at)Yahoo(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, 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-29 15:31:40 |
Message-ID: | 4019275C.4070609@Yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> 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...
Currently the only way to do that would be to have a user defined
function that calls SPI_prepare() with the query string and returns the
desired information to the client.
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck(at)Yahoo(dot)com #
From | Date | Subject | |
---|---|---|---|
Next Message | Christoph Haller | 2004-01-29 16:13:08 | Re: Disaster! |
Previous Message | lnd | 2004-01-29 09:17:11 | Re: Question about indexes |