"Gauthier, Dave" writes:
> 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, a
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
On Thu, Jan 14, 2010 at 3:12 PM, 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
keep going. Nothing from the
entire stream is committed until/unless they're all clean.
Thanks
-Original Message-
From: Joshua D. Drake [mailto:j...@commandprompt.com]
Sent: Thursday, January 14, 2010 6:35 PM
To: Gauthier, Dave
Cc: pgsql-general@postgresql.org
Subject: Re: [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 cons
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: cur
