Message-ID: <gh-postgresql-interfaces-psqlodbc-43-c2373328092@github.com>
From: "KristianIvarsson (@KristianIvarsson)" <noreply+KristianIvarsson@github.com>
To: "postgresql-interfaces/psqlodbc" <noreply+postgresql-interfaces-psqlodbc@github.com>
Date: Wed, 25 Sep 2024 07:52:27 +0000
Subject: Re: [postgresql-interfaces/psqlodbc] issue #43: syntax error at or near "ROWS"
In-Reply-To: <gh-postgresql-interfaces-psqlodbc-43@github.com>
References: <gh-postgresql-interfaces-psqlodbc-43@github.com>
List-Id: <gh-postgresql-interfaces-psqlodbc.github.com>
X-GitHub-Author-Login: KristianIvarsson
X-GitHub-Comment-Id: 2373328092
X-GitHub-Comment-Type: issue_comment
X-GitHub-Edited-At: 2024-10-21T10:18:34Z
X-GitHub-Issue: 43
X-GitHub-Repo: postgresql-interfaces/psqlodbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/postgresql-interfaces/psqlodbc/issues/43#issuecomment-2373328092
Content-Type: text/plain; charset=utf-8

Possibly and I didn't know that it meant they weren't bound

It seems like the parameters are bound if using `OFFSET ? LIMIT ?`-statement, and `SQLExecuteDirect()` so it' doesn't seem to be just about that

As I wrote in the mailing list, `OFFSET ? ROWS FETCH FIRST ? ROWS ONLY` statement seems to work if you add a 3rd string binding parameter in some circumstances (it'd better to read the mailing list thread)

https://www.postgresql.org/message-id/DB9PR01MB9512A7C9601A507899D1D465F1632%40DB9PR01MB9512.eurprd01.prod.exchangelabs.com