From: | Jonathan Barnhart <jdbarnhart(at)yahoo(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Transaction blocks |
Date: | 2004-08-10 20:45:26 |
Message-ID: | 20040810204526.20560.qmail@web53705.mail.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Is there a way to continue a transaction after an error? I've got a
situation where I have a transaction open and I'm inserting data, but
some of it could fail on validation. I want to keep the good stuff,
leave out the bad, and get the speed of not having to commit every
record seperately. For a specific example, I'm importing a list of
stocks, but some symbols have changed because the list is old, so there
are invalid symbols in the list that are not found in the master list.
I want to catch the invalid ones and fix them, but still commit the
good ones. Right now I'm committing each record, but it's slow.
=====
"We'll do the undoable, work the unworkable, scrute the inscrutable and have a long, hard look at the ineffable to see whether it might not be effed after all"
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-08-10 20:54:58 | Re: hostory tables with a generic function? |
Previous Message | Stephan Szabo | 2004-08-10 20:43:09 | Re: Postgres update with self join |