Re: SQL statements error in pgsql 16 but not in pgsql 12 - Mailing list pgsql-sql

From Bharani SV-forum
Subject Re: SQL statements error in pgsql 16 but not in pgsql 12
Date
Msg-id 151842168.569875.1721141786874@mail.yahoo.com
Whole thread Raw
In response to SQL statements error in pgsql 16 but not in pgsql 12  (Frank Komsic <komsicf@shoeicanada.com>)
Responses Re: SQL statements error in pgsql 16 but not in pgsql 12
List pgsql-sql
cross check
WHERE (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 <komsicf@shoeicanada.com> 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

pgsql-sql by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: SQL statements error in pgsql 16 but not in pgsql 12
Next
From: "David G. Johnston"
Date:
Subject: Re: SQL statements error in pgsql 16 but not in pgsql 12