Why ContinueUpdateOnError is not implemented in npgsql

From: "Andrus" <kobruleht2(at)hot(dot)ee>
To: pgsql-general(at)postgresql(dot)org
Subject: Why ContinueUpdateOnError is not implemented in npgsql
Date: 2006-12-29 00:17:38
Message-ID: en1mts$217g$1@news.hub.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

.NET data adapter must implement DataAdapter.ContinueUpdateOnError
property in transaction.

ContinueUpdateOnError requires that transaction continues after error. In
this case .NET can mark all bad rows in DataGrid. User can see all errors
together.

Unfortunately inside transaction after error PostgreSQL returns message

"Current transaction aborted, command ignored after end of transaction
block"

for all subsequent commands.

npgsql does NOT have any support for fix this.
It marks ALL subsequent commands as invalid.
So npgsql cannot used as reliable .NET data provider.
Please confirm this.

There are only two ways fix this issue.
NpgsqlDataAdapter must invoke automatic ROLLBACK after each error
or use checkpoints before each command.

Why this is not implemented ?

SIDENOTE.

In this case PosgreSQL acts like ill-designed compiler or spell checker
which hangs on first error. Todays compilers return as many errors as
possible.
Word spell checker mark all misspelled words in document, not only first
one.
Using PostgreSQL+npgsql to import or edit large amounts of data having minor
errors is huge loss in perfomance since major ADO.NET property is not
supported. After each error whole process must started again.

Andrus

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Bob Pawley 2006-12-29 01:53:36 Re: Backup Restore
Previous Message Martijn van Oosterhout 2006-12-28 22:03:29 Re: Optimising "full outer join where" for muti-row to multi-column view