Re: Why ContinueUpdateOnError is not implemented in npgsql

From: "Andrus" <kobruleht2(at)hot(dot)ee>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Why ContinueUpdateOnError is not implemented in npgsql
Date: 2006-12-29 11:04:08
Message-ID: en2spf$18b8$1@news.hub.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

>> There are only two ways fix this issue.
>> NpgsqlDataAdapter must invoke automatic ROLLBACK after each error
>> or use checkpoints before each command.
>
> Yup, a savepoint before each command is required if that's the behavior
> you want. Yes, that adds overhead. The reason it's not automatic is
> exactly that it adds overhead, which many applications don't need or
> want. But if you have to have it, that's what you do.

If I want to add 10000 records, using savepoint before each INSERT command
makes program very slow.

Why MS SQL server and Oracle does not have this issue and implement
ContinueUpdateOnError fast ?

Is this issue caused by PostgreSQL design failure ?

Andrus.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message vinjvinj 2006-12-29 14:29:00 How to unlock a row
Previous Message Martijn van Oosterhout 2006-12-29 10:23:57 Re: out of memory woes