Re: Problem with aborting entire transactions on error - Mailing list pgsql-general

From Scott Marlowe
Subject Re: Problem with aborting entire transactions on error
Date
Msg-id CAOR=d=2azsiX=r26_WhqAZ666xC2NVMn_FYBKLNnxJJ_uexQ=A@mail.gmail.com
Whole thread Raw
In response to Re: Problem with aborting entire transactions on error  (Zbigniew <zbigniew2011@gmail.com>)
List pgsql-general
On Mon, Dec 10, 2012 at 11:29 AM, Zbigniew <zbigniew2011@gmail.com> wrote:
> 2012/12/10, Scott Marlowe <scott.marlowe@gmail.com>:
>
>> Databases aren't as simple as you imagine.  What you're basically
>> asking for from the pg engine is for it to enclose every insert into a
>> subtransaction (i.e. set a savepoint) to check for an error.
>
> No, I'm not.

Whether you know it or not, that IS what you are asking for.  It's how
pg works.  I'm done.


pgsql-general by date:

Previous
From: Zbigniew
Date:
Subject: Re: Problem with aborting entire transactions on error
Next
From: François Beausoleil
Date:
Subject: Literal NUL using COPY TO