Message-ID: <gh-postgresql-interfaces-psqlodbc-89-c2629033484@github.com>
From: "davecramer (@davecramer)" <noreply+davecramer@github.com>
To: "postgresql-interfaces/psqlodbc" <noreply+postgresql-interfaces-psqlodbc@github.com>
Date: Sat, 01 Feb 2025 17:16:19 +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: 2629033484
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-2629033484
Content-Type: text/plain; charset=utf-8

So if I understand correctly, you would like the insert for the first to succeed and the second to fail.
Since the insert for both is a single transaction when the first fails the second fails as postgres does not commit the transaction. 
This is by design.

see https://www.postgresql.org/docs/current/tutorial-transactions.html for more details

Dave