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 1rnf3R-00EP6w-BA for pgsql-sql@arkaria.postgresql.org; Fri, 22 Mar 2024 13:35:29 +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 1rnf3P-003Zoj-Q7 for pgsql-sql@arkaria.postgresql.org; Fri, 22 Mar 2024 13:35:28 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rnf3P-003Zob-EG for pgsql-sql@lists.postgresql.org; Fri, 22 Mar 2024 13:35:28 +0000 Received: from mail-oo1-xc34.google.com ([2607:f8b0:4864:20::c34]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rnf3N-005uSN-9N for pgsql-sql@lists.postgresql.org; Fri, 22 Mar 2024 13:35:27 +0000 Received: by mail-oo1-xc34.google.com with SMTP id 006d021491bc7-5a4f7a648dbso1102255eaf.3 for ; Fri, 22 Mar 2024 06:35:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1711114523; x=1711719323; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=5nsNdmfmA8MDRhirAzBnhHzHzo1iayALSi4tUFgaqIw=; b=LODMIMEQnjyKf3L4OLgJLTewVugs0wqGRCO4ofLZGRA3JxqzEdtl0mUZcXtecIEBT8 2UQIFeMOZ6Vn3WyZAFw+ib5iX+FIGzMJF4KN0Fkliq02+tQ2+5hNe7bC+rMUptaFcxCB mFC4J6W2RqQ0DO7PJcbCEpXt8KvWjWBoANbfPv62VKQDYkWinr/It1hvMLCL0/M+UgC/ t/1+gTrVDT9CvHPQ2htbExiqlwSTYXjUebqJ23YTkjz7NTqSk1QkSIi8/07+SLhp1bzF 5d/G4WQ6EPCaBAV+jLblxQ5BC44WZHWlVIRwtfyouIbR9Vp1D/i4PpnCXhogxrOLIXpH tYeQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1711114523; x=1711719323; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=5nsNdmfmA8MDRhirAzBnhHzHzo1iayALSi4tUFgaqIw=; b=rcFNkYA3FZAme7UQ1TNrixdZoIsPAdMO7jwVfGYOU/DefnVd7a+FiHhE8JvdxkauF4 rqteM/j3ejMPg5r5fCGxDPFEHvfaBA/GLp1PgFXaqnY5HdaYcSnDgDtnYukPmw/57eYU XGDC5lDUKB9fU6b0rTcup2vs3rVknWUDRdnMqHQfUfoGYzhDFFejgv1zBxVTBY8uJChv LTeN/S8fjb33tihLyLj/r8mUUoh2Lr7v8icEbTlOA8DA/vFgydlP08P3ZdwPkPd9wZKl 5czi2ITHhUpqDY2pUPPzNRvhTXPvwaB0z6t3OttUw/Grr4YXWmT39U3bhA04ZYmovZpQ qZaA== X-Gm-Message-State: AOJu0YybPIXttMOfm5HJNnC+yaTbslod6OqzVRUwUR2fJnndZ31EFSkl Z35A/2XoMpXCfx80FYoItnsnjYI0Zf8eloOGnShmMwupaq0+2ccBmETpgqsXnrHHkwKUD78oxt2 5a3IdSOoyELFdVLb4TIFkFEZgaxj0/mcd X-Google-Smtp-Source: AGHT+IFGPDIs1ANU+zjuaN0J6BUt5cZwqUaEVZ9wosESFLv3DB+H8krBnWZJaL/1d+ZQ4YXAfqeH1NUgt8hYvZRtzDk= X-Received: by 2002:a05:6820:98b:b0:5a5:25b9:dea7 with SMTP id cg11-20020a056820098b00b005a525b9dea7mr790970oob.3.1711114523354; Fri, 22 Mar 2024 06:35:23 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:ac9:7393:0:b0:51b:abdd:416f with HTTP; Fri, 22 Mar 2024 06:35:22 -0700 (PDT) In-Reply-To: References: From: "David G. Johnston" Date: Fri, 22 Mar 2024 06:35:22 -0700 Message-ID: Subject: Re: UPDATE with AND clarification To: Jamie Thompson Cc: "pgsql-sql@lists.postgresql.org" Content-Type: multipart/alternative; boundary="00000000000055ad8a06143fe50a" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000055ad8a06143fe50a Content-Type: text/plain; charset="UTF-8" On Friday, March 22, 2024, Jamie Thompson wrote: > > Earlier today, I was running some sql for someone which they had submitted > as: > > UPDATE tablename SET col1 = val1 AND col2 = val2 WHERE id = X > I presume these columns are booleans. So you wrote something like: Set col1 = ( true and false = true ) Which in this case must coincidentally have produced whatever boolean value already existed in col1. David J. --00000000000055ad8a06143fe50a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Friday, March 22, 2024, Jamie Thompson <jthompson.neuk@gmail.com> wrote:

Earlier today, I was running some sql for some= one which they had submitted as:
> UPDATE=C2=A0tablename SET col1 =3D= val1 AND col2 =3D val2 WHERE id =3D X
<= /blockquote>

I presume these columns are booleans.=C2=A0= So you wrote something like:
Set col1 =3D ( true and false =3D t= rue )

Which in this case must coincidentally have = produced whatever boolean value already existed in col1.

David J.

--00000000000055ad8a06143fe50a--