Re: Why ContinueUpdateOnError is not implemented in npgsql

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Andrus" <kobruleht2(at)hot(dot)ee>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Why ContinueUpdateOnError is not implemented in npgsql
Date: 2006-12-29 04:09:04
Message-ID: 27901.1167365344@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Andrus" <kobruleht2(at)hot(dot)ee> writes:
> ContinueUpdateOnError requires that transaction continues after error. In
> this case .NET can mark all bad rows in DataGrid. User can see all errors
> together.
> ...
> 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.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2006-12-29 04:20:28 Re: ERROR: could not access status of transaction
Previous Message Joshua D. Drake 2006-12-29 03:48:22 Re: questions about migrating form postgres 7 to 8