libpq usage question

From: Joe Conway <mail(at)joeconway(dot)com>
To: pgsql-hackers <pgsql-hackers(at)postgreSQL(dot)org>
Subject: libpq usage question
Date: 2002-03-14 22:52:07
Message-ID: 3C912997.4060001@joeconway.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I'm working on an update to contrib/dblink which would allow
INSERT/UPDATE/DELETE statements in addition to SELECT statements against
a remote database.

In the current version, only SELECT is possible because the SQL
statement passed to the function gets "DECLARE mycursor CURSOR FOR "
appended to the front of it, and the result set is obtained with "res =
PQexec(conn, "FETCH ALL in mycursor");".

My question is, what is the downside (if any) of eliminating the use of
a cursor in this context? I have locally made the changes, and don't see
any negative impact. I'd appreciate any thoughts.

Thanks,

Joe

Browse pgsql-hackers by date

  From Date Subject
Next Message Larry Rosenman 2002-03-14 23:35:23 Re: [SQL] Syslog
Previous Message Ben Grimm 2002-03-14 22:47:39 Re: Bug #613: Sequence values fall back to previously chec