From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Jan Wieck <JanWieck(at)Yahoo(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(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-30 10:50:32 |
Message-ID: | 200401301050.i0UAoW012330@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Jan Wieck wrote:
> 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.
>
Oh, I understand now. Added to TODO:
* Allow libpq to return information about prepared queries
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2004-01-30 11:31:17 | Re: Question about indexes |
Previous Message | Bruce Momjian | 2004-01-30 10:44:30 | Re: Getting the results columns before execution |