Message-ID: <gh-postgresql-interfaces-psqlodbc-102-c2787310949@github.com>
From: "davecramer (@davecramer)" <noreply+davecramer@github.com>
To: "postgresql-interfaces/psqlodbc" <noreply+postgresql-interfaces-psqlodbc@github.com>
Date: Tue, 08 Apr 2025 18:19:08 +0000
Subject: Re: [postgresql-interfaces/psqlodbc] issue #102: Statement using WITH and INSERT does not work when UseDeclareFetch=1
In-Reply-To: <gh-postgresql-interfaces-psqlodbc-102@github.com>
References: <gh-postgresql-interfaces-psqlodbc-102@github.com>
List-Id: <gh-postgresql-interfaces-psqlodbc.github.com>
X-GitHub-Author-Login: davecramer
X-GitHub-Comment-Id: 2787310949
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 102
X-GitHub-Repo: postgresql-interfaces/psqlodbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/postgresql-interfaces/psqlodbc/issues/102#issuecomment-2787310949
Content-Type: text/plain; charset=utf-8

> If there is a way to ODBC "decide" that for some kind of statements the cursor approach does not fit, this will be awesome. But, I can also work around it just turning off UseDeclareFetch.

Well that's sort of exactly what the `UseDeclareFetch` is telling it to do. I'm surprised it is using `WITH HOLD` cursors.