Re: Request for official clarification on SQL parameter parsing changes in PostgreSQL 15 and 16

From: Dominique Devienne <ddevienne(at)gmail(dot)com>
To: 王 博 <bo(dot)wang(at)infortech(dot)co(dot)jp>
Cc: "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>, 李 浩 <hao(dot)li(at)infortech(dot)co(dot)jp>
Subject: Re: Request for official clarification on SQL parameter parsing changes in PostgreSQL 15 and 16
Date: 2025-04-17 09:47:16
Message-ID: CAFCRh-_3XAW3c6385sk7RirOmYacJeadrcsVym2A3wA1TsyAUw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Apr 17, 2025 at 11:13 AM 王　博 <bo(dot)wang(at)infortech(dot)co(dot)jp> wrote:
> Hello PostgreSQL Community,
> We have encountered unexpected SQL parsing errors during application upgrades from PostgreSQL 14 to 15 and 16, related to 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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Ron Johnson 2025-04-17 12:53:50 Re: Cannot turn track_counts on
Previous Message 王　博 2025-04-17 05:17:18 Request for official clarification on SQL parameter parsing changes in PostgreSQL 15 and 16