Re: Request for official clarification on SQL parameter parsing changes in PostgreSQL 15 and 16 - Mailing list pgsql-general

From Dominique Devienne
Subject Re: Request for official clarification on SQL parameter parsing changes in PostgreSQL 15 and 16
Date
Msg-id CAFCRh-_3XAW3c6385sk7RirOmYacJeadrcsVym2A3wA1TsyAUw@mail.gmail.com
Whole thread Raw
In response to Request for official clarification on SQL parameter parsing changes in PostgreSQL 15 and 16  (王 博 <bo.wang@infortech.co.jp>)
List pgsql-general
On Thu, Apr 17, 2025 at 11:13 AM 王 博 <bo.wang@infortech.co.jp> wrote:
> Hello PostgreSQL Community,
> We have encountered unexpected SQL parsing errors during application upgrades from PostgreSQL 14 to 15 and 16,
relatedto the use of JDBC-style parameter placeholders (`?`) in our legacy applications. 

AFAIK, PostgreSQL itself only supports $1, $2, ... bind placeholders.
Thus I suspect it's your JDBC driver that adds support for ? style placeholders.
So look in the release notes for that, instead of PostgreSQL itself. --DD



pgsql-general by date:

Previous
From: 王 博
Date:
Subject: Request for official clarification on SQL parameter parsing changes in PostgreSQL 15 and 16
Next
From: Ron Johnson
Date:
Subject: Re: Cannot turn track_counts on