I think you must explicitly issue a "ROLLBACK" command, reason being I
once created multiple exports to different tables for one form on to
postgres DB and I noticed when I had technical glitch prior ALL exports
being executed some of my records would be missing in my other tables
whilst other tables would populated.
From: Carol Walter [mailto:walterc(at)indiana(dot)edu]
Sent: 17 June 2009 14:27
Subject: [NOVICE] implicit rollback?
I have a program (PHP) that is executing a number of SQL commands as a
single transaction. At the beginning of the transaction, I have a
"BEGIN" and at the end I have a "COMMIT". If one of the transactions
fails, do I have to explicitly issue a "ROLLBACK" command, or will
postgres do this automatically because one of the commands fails?
In response to
pgsql-novice by date
|Next:||From: John DeSoi||Date: 2009-06-17 18:33:42|
|Subject: Re: implicit rollback?|
|Previous:||From: Carol Walter||Date: 2009-06-17 12:26:30|
|Subject: implicit rollback?|