From: | Atif Jung <atifjung(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-novice(at)postgresql(dot)org |
Subject: | Re: DECLARE CURSOR |
Date: | 2010-06-28 15:45:32 |
Message-ID: | AANLkTikAo3LLSxxxX5pNA6s-R1-Y3T8SzIKTikJh-PWj@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
Thanks Tom,
The postgres manual states:
"In the default mode, statements are committed only when EXEC SQL COMMIT is
issued. The embedded SQL interface also supports autocommit of transactions
(similar to libpq behavior) via the -t command-line option to ecpg (see
below) or via the EXEC SQL SET AUTOCOMMIT TO ON statement. In autocommit
mode, each command is automatically committed unless it is inside an
explicit transaction block. This mode can be explicitly turned off using
EXEC SQL SET AUTOCOMMIT TO OFF."
I've used the -t command-line option when compiling my code, and AUTOCOMMIT
is set, but I still get the following error message whenever I OPEN a cursor
I've already DECLARED.
DECLARE CURSOR can only be used in transaction blocks.
What am I doing wrong?
Thanks
Atif
On 28 June 2010 15:00, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Atif Jung <atifjung(at)gmail(dot)com> writes:
> > I'm getting an error msg which reads:
> > DECLARE CURSOR can only be used in transaction blocks.
>
> > does that mean to DECLARE a cursor I must surrond it with a BEGIN &
> COMMIT
> > work?
>
> Yes. The cursor automatically disappears as soon as you commit, so it'd
> be useless otherwise.
>
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | Greg | 2010-06-28 16:31:54 | Postgre Protocol |
Previous Message | Atif Jung | 2010-06-28 14:56:51 | AUTO COMMIT |