From: | Chip Gobs <chip(dot)gobs(at)noaa(dot)gov> |
---|---|
To: | pgsql-interfaces(at)postgresql(dot)org |
Subject: | Implicit Transactions and Rolling Back |
Date: | 2004-09-20 12:05:43 |
Message-ID: | 414EC797.202C8C76@noaa.gov |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
We are porting from Informix to PostgreSQL 7.4.5 and have noticed the
following behavior.
If we try to OPEN a CURSOR for an invalid SELECT statement in ECPG, we
get an error, as expected. However, if we then attempt to OPEN another
CURSOR for a valid statement,
we get an error that says we are in a failed transaction. At that
point, no statement will succeed.
The only way we have found to get out of this state is to ROLLBACK
explicitly.
We are not using explicit transactions. My understanding is that PG
should be rolling back failed statements
when we are not in an explicit transaction.
Do we have an incorrect setting, a misunderstanding of how it is
supposed to work, or a bug? Could anyone enlighten me?
Thanks,
Chip
From | Date | Subject | |
---|---|---|---|
Next Message | Kathy Smith | 2004-09-21 15:32:47 | Re: Adding null values to arrays |
Previous Message | David Stanaway | 2004-09-13 21:45:19 | Re: [PATCH] add notice processor to DBD::Pg |