Re: ECPG: AUTOCOMMIT and CURSORs

That would explain it. I was neither in a transaction nor did any explicit HOLD.
Thanks Kevin.

________________________________
From: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: pgsql-admin(at)postgresql(dot)org; A J <s5aly(at)yahoo(dot)com>
Sent: Mon, October 4, 2010 5:20:14 PM
Subject: Re: [ADMIN] ECPG: AUTOCOMMIT and CURSORs

A J <s5aly(at)yahoo(dot)com> wrote:

> I am seeing some funny behavior on using both:
> EXEC SQL SET AUTOCOMMIT TO ON;
> and
> CURSORS (EXEC SQL DECLARE ............., EXEC SQL FETCH NEXT FROM
> .............)
>
> On autocommit on (either through above method or precompiling with
> -t option),
> the cursor does not return any rows. On disabling autocommit, I
> get the required number of rows from the cursor.
>
> Any idea what could be going on ?

Are you inside of a transaction? How does the WITH or WITHOUT HOLD
function in ECPG? From the manual:

http://www.postgresql.org/docs/current/interactive/sql-declare.html

"WITHOUT HOLD specifies that the cursor cannot be used outside of
the transaction that created it. If neither WITHOUT HOLD nor WITH
HOLD is specified, WITHOUT HOLD is the default."

-Kevin