Re: Problem with aborting entire transactions on error

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: Zbigniew <zbigniew2011(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Problem with aborting entire transactions on error
Date: 2012-12-10 18:35:38
Message-ID: CAOR=d=2azsiX=r26_WhqAZ666xC2NVMn_FYBKLNnxJJ_uexQ=A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Dec 10, 2012 at 11:29 AM, Zbigniew <zbigniew2011(at)gmail(dot)com> wrote:
> 2012/12/10, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)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.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message François Beausoleil 2012-12-10 18:40:51 Literal NUL using COPY TO
Previous Message Zbigniew 2012-12-10 18:29:49 Re: Problem with aborting entire transactions on error