public inbox for [email protected]
help / color / mirror / Atom feedFrom: Frank Komsic <[email protected]>
To: David G. Johnston <[email protected]>
Cc: [email protected] <[email protected]>
Subject: Re: SQL statements error in pgsql 16 but not in pgsql 12
Date: Tue, 16 Jul 2024 18:01:35 +0000
Message-ID: <BL3PR05MB92365E0925E92F6830C83229B3A22@BL3PR05MB9236.namprd05.prod.outlook.com> (raw)
In-Reply-To: <CAKFQuwb1Fugw3jQGuqPQZBPZjQyskBi=TzpP5vjM+bDKmFhFhg@mail.gmail.com>
References: <DM4PR05MB92551C285B81BB5FB12F1BC6B3A12@DM4PR05MB9255.namprd05.prod.outlook.com>
<CAKFQuwb1Fugw3jQGuqPQZBPZjQyskBi=TzpP5vjM+bDKmFhFhg@mail.gmail.com>
Thank you for your reply.
I gather I will have to lookover the entire code and set the SQL statements correctly.
Thanks
Frank
From: David G. Johnston <[email protected]>
Date: Monday, July 15, 2024 at 7:24 PM
To: Frank Komsic <[email protected]>
Cc: [email protected] <[email protected]>
Subject: Re: SQL statements error in pgsql 16 but not in pgsql 12
On Mon, Jul 15, 2024 at 3:57 PM Frank Komsic <[email protected]<mailto:[email protected]>> wrote:
The above sql command works in version 12 but does not work in version 16 due to missing space in “WHERE (lot = 19749OR lot= 19750)”
Why did this work before and now it does not work?
It seems to be a side-effect of supporting non-decimal literals.
https://www.postgresql.org/message-id/flat/[email protected]
Git: 6fcda9aba83449082124825b6d375c0a61e21c42
This comment in particular refers to a v15 change that is probably related if you want to dive deeper.
https://www.postgresql.org/message-id/flat/1467947.1669851407%40sss.pgh.pa.us#66391c571b4db866e22245...
Suffice to say, we became more strict here since v12 and you will need to modify the query accordingly.
David J.
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: SQL statements error in pgsql 16 but not in pgsql 12
In-Reply-To: <BL3PR05MB92365E0925E92F6830C83229B3A22@BL3PR05MB9236.namprd05.prod.outlook.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox