Re: BUG #18606: syntax error at or near "ROWS" - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #18606: syntax error at or near "ROWS"
Date
Msg-id 3145581.1725892966@sss.pgh.pa.us
Whole thread Raw
In response to BUG #18606: syntax error at or near "ROWS"  (PG Bug reporting form <noreply@postgresql.org>)
List pgsql-bugs
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



pgsql-bugs by date:

Previous
From: Thomas Munro
Date:
Subject: Re: BUG #18146: Rows reappearing in Tables after Auto-Vacuum Failure in PostgreSQL on Windows
Next
From: PG Bug reporting form
Date:
Subject: BUG #18607: UNION ALL discards all foreign key relations + indexes