Skip site navigation (1) Skip section navigation (2)

Re: PostgreSQL 8.3, libpq and WHERE CURRENT OF

From: Sebastien FLAESCH <sf(at)4js(dot)com>
To: Heikki Linnakangas <heikki(at)enterprisedb(dot)com>
Cc: 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 12:34:23
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Thanks Heikki for this quick answer.

Actually we do the following lipq calls:

- PQPrepare(... "SELECT ... FROM ... FOR UPDATE" ... )
- PQexecPrepared(...)
- PQntuples(...) / PQgetvalue(...)

i.e. we don't use the DECLARE CURSOR instruction, we just prepare/execute
the plain SELECT statement (with potential parameters)...

I can't remember why but there was some limitation or problems to use the
DECLARE CURSOR in our context... must dig in my mail archive to give you
more details...

FYI we do actually a PostgreSQL driver for our runtime VM...

Does a simple PQPrepare() with a SELECT statement not create a cursor on
the server side? If yes, would it not be possible to pass a cursor name
as in ODBC?

Best regards,

Heikki Linnakangas wrote:
> Sebastien FLAESCH wrote:
>> Just looked at the new features of 8.3 and realized that positioned
>> updates/deletes is now possible with this new release...
>> We would use that if we could define the cursor name with a libpq function.
> I don't understand. When you open a cursor with DECLARE CURSOR, you give
> it a name. Doesn't that do what you want?

In response to


pgsql-hackers by date

Next:From: Tom LaneDate: 2007-10-26 12:34:49
Subject: Re: PANIC caused by open_sync on Linux
Previous:From: Magnus HaganderDate: 2007-10-26 12:29:51
Subject: Re: 8.2.3: Server crashes on Windows using Eclipse/Junit

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group