| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | "Gauthier, Dave" <dave(dot)gauthier(at)intel(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Avoid transaction abot if/when constraint violated |
| Date: | 2010-01-14 23:35:14 |
| Message-ID: | 1263512114.20966.824.camel@jd-desktop.unknown.charter.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, 2010-01-14 at 15:12 -0700, 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?
Only if it is a foreign key issue in which case you can defer the check.
If it is a single transaction, and you insert a bad record the whole
transaction fails.
Joshua D. Drake
>
>
>
> Thanks in Advance!
>
>
--
PostgreSQL.org Major Contributor
Command Prompt, Inc: http://www.commandprompt.com/ - 503.667.4564
Consulting, Training, Support, Custom Development, Engineering
Respect is earned, not gained through arbitrary and repetitive use or Mr. or Sir.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gauthier, Dave | 2010-01-14 23:40:57 | Re: Avoid transaction abot if/when constraint violated |
| Previous Message | Gauthier, Dave | 2010-01-14 22:12:16 | Avoid transaction abot if/when constraint violated |