Error abort transaction behaviour
As I can read from other appends then the behaviour where transactions
are aborted if errors occur is "working as designed" in PostgreSQL.
This is different from the behaviour in DB/2 and Oracle (eg. they do
not abort a transaction if a dulicated key is inserted into a table)
and makes it almost impossible for me to have common code that can use
both PostgreSQL, DB/2 and Oracle.
I'm using PostgreSQL 7.2. Is this something that will be changed in a
later version of PostgreSQL?
Best regards
Thomas
hyldgaard@hotmail.com (Thomas Hyldgaard) writes:
As I can read from other appends then the behaviour where transactions
are aborted if errors occur is "working as designed" in PostgreSQL.
I'm using PostgreSQL 7.2. Is this something that will be changed in a
later version of PostgreSQL?
Maybe someday, but it's not just around the corner.
regards, tom lane
Tom Lane wrote:
hyldgaard@hotmail.com (Thomas Hyldgaard) writes:
As I can read from other appends then the behaviour where transactions
are aborted if errors occur is "working as designed" in PostgreSQL.
I'm using PostgreSQL 7.2. Is this something that will be changed in a
later version of PostgreSQL?Maybe someday, but it's not just around the corner.
Yes, nested transactions/savepoints is what we need.
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026