Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.600.62\))
Subject: Re: Updating 457 rows in a table
From: Christophe Pettus <xof@thebuild.com>
In-Reply-To: <98639d1a-dddf-38e3-49b3-63632136a0f@appl-ecosys.com>
Date: Sun, 19 May 2024 11:32:39 -0700
Cc: pgsql-general@lists.postgresql.org
Content-Transfer-Encoding: 7bit
Message-Id: <372F0968-BD78-45EB-AE70-015DBF923EBC@thebuild.com>
References: <164b3681-7a42-1e5-6a7b-80196ed33ded@appl-ecosys.com>
 <1E14886A-BBCB-40E4-8231-1159D12BD261@thebuild.com>
 <98639d1a-dddf-38e3-49b3-63632136a0f@appl-ecosys.com>
To: Rich Shepard <rshepard@appl-ecosys.com>
Archived-At: <https://www.postgresql.org/message-id/372F0968-BD78-45EB-AE70-015DBF923EBC%40thebuild.com>
Precedence: bulk


> On May 19, 2024, at 11:30, Rich Shepard <rshepard@appl-ecosys.com> wrote:
> That's a good idea; I can use a predicate to identify the rows to update.
> That would be shorter than a long, comma-separated list.

Of course, you can probably also shorten the query to:

	UPDATE people SET active=true WHERE ...

Where ... is the predicate you would have used in the SELECT id WHERE ...