| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | komsicf(at)shoeicanada(dot)com |
| Cc: | "pgsql-sql(at)lists(dot)postgresql(dot)org" <pgsql-sql(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: SQL statements error in pgsql 16 but not in pgsql 12 |
| Date: | 2024-07-15 23:23:42 |
| Message-ID: | CAKFQuwb1Fugw3jQGuqPQZBPZjQyskBi=TzpP5vjM+bDKmFhFhg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
On Mon, Jul 15, 2024 at 3:57 PM Frank Komsic <komsicf(at)shoeicanada(dot)com>
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/b239564c-cad0-b23e-c57e-166d883cb97d(at)enterprisedb(dot)com
Git: 6fcda9aba83449082124825b6d375c0a61e21c42
This comment in particular refers to a v15 change that is probably related
if you want to dive deeper.
Suffice to say, we became more strict here since v12 and you will need to
modify the query accordingly.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bharani SV-forum | 2024-07-16 14:56:26 | Re: SQL statements error in pgsql 16 but not in pgsql 12 |
| Previous Message | Frank Komsic | 2024-07-15 22:57:24 | SQL statements error in pgsql 16 but not in pgsql 12 |