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.96) (envelope-from ) id 1vOI6c-001AgI-0i for pgsql-general@arkaria.postgresql.org; Wed, 26 Nov 2025 16:10:58 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vOI6a-000JM9-2j for pgsql-general@arkaria.postgresql.org; Wed, 26 Nov 2025 16:10:57 +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.96) (envelope-from ) id 1vOI6a-000JLu-1h for pgsql-general@lists.postgresql.org; Wed, 26 Nov 2025 16:10:56 +0000 Received: from mail.appl-ecosys.com ([50.126.108.78]) by makus.postgresql.org with smtp (Exim 4.96) (envelope-from ) id 1vOI6Y-001bBW-1i for pgsql-general@lists.postgresql.org; Wed, 26 Nov 2025 16:10:55 +0000 Received: from salmo.appl-ecosys.com (salmo.appl-ecosys.com [192.168.55.1]) by mail.appl-ecosys.com (Postfix) with ESMTP id 8BF8A2A14D6 for ; Wed, 26 Nov 2025 08:10:54 -0800 (PST) Date: Wed, 26 Nov 2025 08:10:54 -0800 (PST) From: Rich Shepard cc: "pgsql-general@lists.postgresql.org" Subject: Re: Selecting all variations of job title in a list In-Reply-To: Message-ID: <989b6fd-2979-8ac6-13b-3916d2e47de8@appl-ecosys.com> References: <20251126154844.e6e3d5c7f476cc966fc201f4@wanadoo.fr> <29ffee7e-40a8-f911-4419-24ba8558f5db@appl-ecosys.com> <20251126164356.9a3b7fc25d5118e28175f9a4@wanadoo.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Wed, 26 Nov 2025, David G. Johnston wrote: > I was using this tool a while back when I was doing heavy regex work. > > https://www.regexbuddy.com/ > > Keep in mind the native flavor of regex in PostgreSQL is TCL, not Perl. > > But I=E2=80=99d still say regexp is not the best solution here - unless= you > encapsulate the logic in a function. I suspect you=E2=80=99ll want to = use this > logic in more than just a single query and with a literal regexp you ha= ve > to rely on manual synchronization. Note, you could combine the lookup > table with regexes. Though beware of ensure you don=E2=80=99t produce = duplicate > matches if you go that route. David, Thanks, Rich