Hi,
I've got the weird behaviour in an ecpg programme that when I issue
EXEC SQL SET AUTOCOMMIT TO ON;
transactions behave as one would expect, i.e. I can use BEGIN
WORK/COMMIT/ROLLBACK, but when I set
EXEC SQL SET AUTOCOMMIT TO OFF;
every statement is wrapped in its own transaction, whether I have issued
a BEGIN WORK or not. This seems a tad counter-intuitive. Previous
discussions on the mailing list seem to suggest that it should be the
other way round?
This is on 7.1RC1 on Linux.
Cheers,
Adriaan