Re: PostgreSQL 8.3, libpq and WHERE CURRENT OF

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Sebastien FLAESCH <sf(at)4js(dot)com>
Cc: Heikki Linnakangas <heikki(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org, Guillaume ERGAND <ger(at)4js(dot)com>
Subject: Re: PostgreSQL 8.3, libpq and WHERE CURRENT OF
Date: 2007-10-26 13:09:42
Message-ID: 10801.1193404182@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Sebastien FLAESCH <sf(at)4js(dot)com> writes:
> Does a simple PQPrepare() with a SELECT statement not create a cursor on
> the server side?

No. A prepared statement is just a query plan, not a query-in-progress.

The Bind/Execute messages sent by PQexecPrepared create something akin
to a cursor, but libpq doesn't expose any API for fetching one row at a
time in that context, so there's no way to use the "current row" anyway.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jignesh K. Shah 2007-10-26 13:20:36 Re: 8.3beta1 testing on Solaris
Previous Message Jonah H. Harris 2007-10-26 13:01:14 Re: PANIC caused by open_sync on Linux