Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sTV3U-00GrVF-3i for pgsql-sql@arkaria.postgresql.org; Mon, 15 Jul 2024 23:24:28 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sTV3R-00Dt4q-Rp for pgsql-sql@arkaria.postgresql.org; Mon, 15 Jul 2024 23:24:25 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sTV3R-00Dt4i-GN for pgsql-sql@lists.postgresql.org; Mon, 15 Jul 2024 23:24:25 +0000 Received: from mail-ot1-x333.google.com ([2607:f8b0:4864:20::333]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sTV3O-002F6L-Nw for pgsql-sql@lists.postgresql.org; Mon, 15 Jul 2024 23:24:24 +0000 Received: by mail-ot1-x333.google.com with SMTP id 46e09a7af769-708bf659898so1384571a34.2 for ; Mon, 15 Jul 2024 16:24:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1721085861; x=1721690661; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=sQCBq+j+sMw+DmRk7CzSgVdtqZAu6k/yslgXehM2YuU=; b=NiUdb9Gm/KTw6/y2IBV60VlfyI8zJW0deNZpWtH+QW4kZzja7uu+VuIssS/eSqe/pP nBfWOgnv/xxDAlGBf437rKG+bjtn+01XlixUqbTn9hTz2+gDwXhi15hS4W2GMtFeDv5+ ikI1vdkMEt/ST/vvJPhNf6jYf3hc7bRGr9C4Z51tkIJyKXhFXbxJQ5QPvyMWXxv4CITa nbc6qowEZQTpgkS6Fm+0PxUudPO785jm+6JHI6hYRxg+CI64krpZziP9a1T2Xl6rMLmm 22AjahnsDYW/3kPb//w6hIUYAGMTu55F1y//5CY0V/j1OANNiJWFRaCP9O50HxUFl40i tzeQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1721085861; x=1721690661; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=sQCBq+j+sMw+DmRk7CzSgVdtqZAu6k/yslgXehM2YuU=; b=CHkaKWiEhzwAYtX55fwnjU+ePJjoEgQ+fwoSkhIg3mxU20Xn4ZEejlazRkW++h+czS BniAvSkyyUmN1hCj/oNh+Jb6eeFaAm6rpAmw8JSGbfm4I/Yov6Vaby7Oh7YQm5CoZpVy ofUPsHfaKC0juQce0/izKFcvFTPsvagkTZuJdxNULp0YqMw1/DuWOMESH/1EFU9t2seb QwEbxCwHQhCLMqIsdTfnNjWj/Q/tbsK9XZsb5n3ZVSzzTsypkb5Np4rkYOv3AdSdoZaR EFGG7cC3VvDTf+8WrpcKzUuUxg/d7lzLO7e1y8IiprddYWM+YSg1hX7zaEFwOzrtiRk1 aUqA== X-Gm-Message-State: AOJu0YwCJoGJc6i4Q1XK52jvPy5plM0KzhSSkJbeRdN7hP8RXgOkeEWF HWe1aHZ+UdtKtGadk5Z4BrLwkciCIyKMTyaPtEKv8nHvuwj8js7hqjRxPkenT/4CtUIcHwWAZnv 0PbadV4RyI6w0/FbSl4/14FWM/SDx23ks X-Google-Smtp-Source: AGHT+IHTm71dNZp+WJC9tW5xtDPTue2BVq8hEAIOInhBZQitL4lqe84juXtYvqaA+O8/Jxzq/DcXpE1iwc1IX9NAN38= X-Received: by 2002:a05:6871:e022:b0:25e:5ff:758b with SMTP id 586e51a60fabf-260bdd27f50mr267658fac.4.1721085861341; Mon, 15 Jul 2024 16:24:21 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: "David G. Johnston" Date: Mon, 15 Jul 2024 16:23:42 -0700 Message-ID: Subject: Re: SQL statements error in pgsql 16 but not in pgsql 12 To: komsicf@shoeicanada.com Cc: "pgsql-sql@lists.postgresql.org" Content-Type: multipart/alternative; boundary="00000000000064b1d8061d518717" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000064b1d8061d518717 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, Jul 15, 2024 at 3:57=E2=80=AFPM Frank Komsic wrote: > The above sql command works in version 12 but does not work in version 16 > due to missing space in =E2=80=9CWHERE (lot =3D 19749OR lot=3D 19750)=E2= =80=9D > > > > 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-166d883c= b97d@enterprisedb.com 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#66391c571b4db866e222450fb3fa9eb9 Suffice to say, we became more strict here since v12 and you will need to modify the query accordingly. David J. --00000000000064b1d8061d518717 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Mon, Jul 15, 2024 at 3:57=E2=80=AFPM Frank Komsic <<= a href=3D"mailto:komsicf@shoeicanada.com">komsicf@shoeicanada.com> w= rote:

The above sql co= mmand works in version 12 but does not work in version 16 due to missing sp= ace in =E2=80=9CWHERE (lot =3D 19749OR lot=3D 19750)=E2=80=9D

=C2=A0=

Why did this wor= k before and now it does not work?

=C2=A0


It seems to be= a side-effect of supporting non-decimal literals.

Git: 6= fcda9aba83449082124825b6d375c0a61e21c42

This comme= nt in particular=C2=A0refers to a v15 change that is probably related if yo= u want to dive deeper.

https://www.postgresql.org/message-id/flat/1467947.1669851= 407%40sss.pgh.pa.us#66391c571b4db866e222450fb3fa9eb9

Suffice to say, we became more strict here since v12 and you will ne= ed to modify the query accordingly.

David J.
--00000000000064b1d8061d518717--