Message-ID: <gh-postgresql-interfaces-psqlodbc-89-c2629246194@github.com>
From: "davecramer (@davecramer)" <noreply+davecramer@github.com>
To: "postgresql-interfaces/psqlodbc" <noreply+postgresql-interfaces-psqlodbc@github.com>
Date: Sun, 02 Feb 2025 05:08:51 +0000
Subject: Re: [postgresql-interfaces/psqlodbc] issue #89: Batch update with some invalid values fails for all rows
In-Reply-To: <gh-postgresql-interfaces-psqlodbc-89@github.com>
References: <gh-postgresql-interfaces-psqlodbc-89@github.com>
List-Id: <gh-postgresql-interfaces-psqlodbc.github.com>
X-GitHub-Author-Login: davecramer
X-GitHub-Comment-Id: 2629246194
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 89
X-GitHub-Repo: postgresql-interfaces/psqlodbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/postgresql-interfaces/psqlodbc/issues/89#issuecomment-2629246194
Content-Type: text/plain; charset=utf-8

Unfortunately the server does not provide that information. It doesn't know that the first one succeeded since it was all done in one insert.

```
insert into testtab1 values (1,'blah');
ERROR:  duplicate key value violates unique constraint "testtab1_pkey"
DETAIL:  Key (id)=(1) already exists.
```
While we do get the error message, we don't know if it is the 1st or 2nd value that failed