From: Jan Bakuwel <jan.bakuwel@greenpeace.org>
To: pgsql-sql@postgresql.org
Subject: Re: Current transaction is aborted, commands ignored until end of transaction block
Date: Fri, 30 Dec 2011 21:43:38 +1300
Message-ID: <4EFD79BA.50508@greenpeace.org> (raw)
In-Reply-To: <13131805-BCBB-42DF-953B-27EE36AAF213@yahoo.com>
References: <4EFD3D32.9060902@greenpeace.org>
<13131805-BCBB-42DF-953B-27EE36AAF213@yahoo.com>
Hi David,
> Start a "savepoint" before each sub-update and rollback to the savepoint if the update fails, and then try again with different data. If it succeeds you then release the savepoint anad move on.
Yeah... not ideal in my case & will result in "messy" code...
Would be nice to have an option in PostgreSQL something along the lines
of: 'abort-transaction-on-constraint-violation = false'....
Jan
Attachments:
[application/pkcs7-signature] smime.p7s (5.6K, ../4EFD79BA.50508@greenpeace.org/2-smime.p7s)
download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: jan.bakuwel@greenpeace.org
Subject: Re: Current transaction is aborted, commands ignored until end of transaction block
In-Reply-To: <4EFD79BA.50508@greenpeace.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox