| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bharani SV-forum <esteembsv-forum(at)yahoo(dot)com> |
| Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, "pgsql-sql(at)lists(dot)postgresql(dot)org" <pgsql-sql(at)lists(dot)postgresql(dot)org>, Frank Komsic <komsicf(at)shoeicanada(dot)com> |
| Subject: | Re: SQL statements error in pgsql 16 but not in pgsql 12 |
| Date: | 2024-07-18 14:57:40 |
| Message-ID: | 3709211.1721314660@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
Bharani SV-forum <esteembsv-forum(at)yahoo(dot)com> writes:
> tagged mean " add to something "
> hope ur picture posted with the sql query, i can see asWHERE (lot = 19749OR lot= 19750)instead of
> WHERE (lot = 19749 OR lot= 19750)
That's not a great choice of word. In any case, the point here
is that the SQL standard requires some whitespace between a number
and a following word, and starting from PG 15 we're enforcing that
to reduce ambiguity.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Frank Komsic | 2024-07-20 17:01:37 | Using replication to upgrade db from 12 to 16 |
| Previous Message | Bharani SV-forum | 2024-07-18 14:50:14 | Re: SQL statements error in pgsql 16 but not in pgsql 12 |