public inbox for [email protected]  

help / color / mirror / Atom feed

From: Bharani SV-forum <[email protected]>
To: [email protected] <[email protected]>
To: Frank Komsic <[email protected]>
Subject: Re: SQL statements error in pgsql 16 but not in pgsql 12
Date: Tue, 16 Jul 2024 14:56:26 +0000 (UTC)
Message-ID: <[email protected]> (raw)
In-Reply-To: <DM4PR05MB92551C285B81BB5FB12F1BC6B3A12@DM4PR05MB9255.namprd05.prod.outlook.com>
References: <DM4PR05MB92551C285B81BB5FB12F1BC6B3A12@DM4PR05MB9255.namprd05.prod.outlook.com>

 cross checkWHERE (lot = 19749 OR lot= 19750)

where the OR is tagged to numeric 19749.
    On Monday, July 15, 2024 at 06:58:06 PM EDT, Frank Komsic <[email protected]> wrote:  
 
  
Hi,
 
  
 
I was trying to upgrade our database from version 12.18 to the latest 16.3
 
  
 
After upgrading, the application has reported errors or “junk info” in the sql command line.
 
  
 
Example SQL code:
 
Message: ERROR: 42601: trailing junk after numeric literal at or near "19749O"
SQL: SELECT bb,mass,classifier,lot
FROM lab.pt_f003_view
WHERE (lot = 19749OR lot= 19750)
ORDER BY lot,bb
 
  
 
  
 
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?
 
  
 
Thanks
 
  
 
Frank Komsic
   

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: <[email protected]>

* 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