Thread: BUG #18606: syntax error at or near "ROWS"

The following bug has been logged on the website:

Bug reference:      18606
Logged by:          Kristian Ivarsson
Email address:      kristone@hotmail.com
PostgreSQL version: 16.4
Operating system:   Microsoft Windows 10 Enterprise Version 10.0.19044
Description:

Using installed version16.4 (even though SQL_DBMS_NAME says version 16.0.4)
with driver PSQLODBC35W.DLL version 13.02.0000)

This error occurs only with some statements when using binding parameters
through ODBC

This statement is an example of when the error occurs

```SELECT "Id","Begin","End","Logfile" FROM "ServerSession" ORDER BY "Begin"
ASC OFFSET ? ROWS FETCH FIRST ? ROW ONLY```

but some more complex SQL statements (with ```OFFSET ? ROWS FETCH FIRST ?
ROW ONLY```) works just fine

Having fixed values (e.g. ```OFFSET 100 ROWS FETCH FIRST 10 ROW ONLY```)
works just fine

I still haven't figured out the pattern what the differences really are that
make some statements to work and some not to work (I haved dugged into the
open source code at all (yet))

/ Kristian

PG Bug reporting form <noreply@postgresql.org> writes:
> This error occurs only with some statements when using binding parameters
> through ODBC

> This statement is an example of when the error occurs

> ```SELECT "Id","Begin","End","Logfile" FROM "ServerSession" ORDER BY "Begin"
> ASC OFFSET ? ROWS FETCH FIRST ? ROW ONLY```

Hmm, what that should look like when it gets to the server,
I imagine, is

  SELECT "Id","Begin","End","Logfile" FROM "ServerSession" ORDER BY "Begin"
  ASC OFFSET $1 ROWS FETCH FIRST $2 ROW ONLY;

which works just fine for me.  I'd suggest peeking into the postmaster
log to see what ODBC is actually sending in the problem cases.  I'm
guessing that pgsql_odbc is doing something bizarre, in which case
you'd be best advised to report this on the pgsql-odbc mailing list.

            regards, tom lane