Message-ID: <gh-postgresql-interfaces-psqlodbc-89-c2629035922@github.com>
From: "vadz (@vadz)" <noreply+vadz@github.com>
To: "postgresql-interfaces/psqlodbc" <noreply+postgresql-interfaces-psqlodbc@github.com>
Date: Sat, 01 Feb 2025 17:23:12 +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: vadz
X-GitHub-Comment-Id: 2629035922
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-2629035922
Content-Type: text/plain; charset=utf-8

Not quite, I'm perfectly fine with the insert failing and actually think this is more correct than doing a partial insert as some other databases/ODBC drivers do. But it would be great to have some information about which rows resulted in an error and this is something that `SQL_ATTR_PARAM_STATUS_PTR` is supposed to provide, but this driver returns `SQL_PARAM_ERROR` in it even for the first row, which would have succeeded.

I.e. the problem is not (so much) returning `SQL_ERROR` instead of `SQL_SUCCESS_WITH_INFO` (although this is inconsistent with the other ODBC drivers I've tried), but not providing any useful information in the status array.