Gauthier, Dave wrote:
Hello !
I have a long list of records I want to insert into a table in such a
way as I can trap and report any/all constraint violations before
rolling back (or opting to commit). Unfortunately, after I hit the
first constraint violation, it aborts the transaction, and then
reports “ERROR: current transaction is aborted, commands ignored until
end of transaction block”.
Is there a way around this?
use savepoints inside the transaction for each insert. your app will
have to figure out how to track the errors if it wants to postpone any
rollback/commit decision til the end.
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
