MIME-Version: 1.0
In-Reply-To: <20251126164356.9a3b7fc25d5118e28175f9a4@wanadoo.fr>
References: <c5296761-2f10-a59b-ad16-a0189e57cd5a@appl-ecosys.com>
 <20251126154844.e6e3d5c7f476cc966fc201f4@wanadoo.fr> <29ffee7e-40a8-f911-4419-24ba8558f5db@appl-ecosys.com>
 <20251126164356.9a3b7fc25d5118e28175f9a4@wanadoo.fr>
From: "David G. Johnston" <david.g.johnston@gmail.com>
Date: Wed, 26 Nov 2025 08:52:03 -0700
Message-ID: <CAKFQuwY2W1WB2qnMuhJ7=GD_rgNmm+N=a7_ZHEtuudw=qajJwg@mail.gmail.com>
Subject: Re: Selecting all variations of job title in a list
To: Vincent Veyron <vv.lists@wanadoo.fr>
Cc: Rich Shepard <rshepard@appl-ecosys.com>, 
	"pgsql-general@lists.postgresql.org" <pgsql-general@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000b01c5006448160b4"
Archived-At: <https://www.postgresql.org/message-id/CAKFQuwY2W1WB2qnMuhJ7%3DGD_rgNmm%2BN%3Da7_ZHEtuudw%3DqajJwg%40mail.gmail.com>
Precedence: bulk

--000000000000b01c5006448160b4
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Wednesday, November 26, 2025, Vincent Veyron <vv.lists@wanadoo.fr> wrote=
:

> On Wed, 26 Nov 2025 07:10:16 -0800 (PST)
> Rich Shepard <rshepard@appl-ecosys.com> wrote:
>
> >
> > Learning postgres regexp is at the top of my list.
> >
>
> https://perldoc.perl.org/perlre
>
> Read the first few pages and you'll be good to go.
>

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 have
to rely on manual synchronization.  Note, you could combine the lookup
table with regexes.  Though beware of ensure you don=E2=80=99t produce dupl=
icate
matches if you go that route.

David J.

--000000000000b01c5006448160b4
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Wednesday, November 26, 2025, Vincent Veyron &lt;<a href=3D"mailto:vv.li=
sts@wanadoo.fr">vv.lists@wanadoo.fr</a>&gt; wrote:<br><blockquote class=3D"=
gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-=
left:1ex">On Wed, 26 Nov 2025 07:10:16 -0800 (PST)<br>
Rich Shepard &lt;<a href=3D"mailto:rshepard@appl-ecosys.com">rshepard@appl-=
ecosys.com</a>&gt; wrote:<br>
<br>
&gt; <br>
&gt; Learning postgres regexp is at the top of my list.<br>
&gt; <br>
<br>
<a href=3D"https://perldoc.perl.org/perlre" target=3D"_blank">https://perld=
oc.perl.org/<wbr>perlre</a><br>
<br>
Read the first few pages and you&#39;ll be good to go.<br>
</blockquote><div><br></div><div>I was using this tool a while back when I =
was doing heavy regex work.</div><div><br></div><div><a href=3D"https://www=
.regexbuddy.com/">https://www.regexbuddy.com/</a><br></div><div><br></div><=
div>Keep in mind the native flavor of regex in PostgreSQL is TCL, not Perl.=
</div><div><br></div><div>But I=E2=80=99d still say regexp is not the best =
solution here - unless you encapsulate the logic in a function.=C2=A0 I sus=
pect you=E2=80=99ll want to use this logic in more than just a single query=
 and with a literal regexp you have to rely on manual synchronization.=C2=
=A0 Note, you could combine the lookup table with regexes.=C2=A0 Though bew=
are of ensure you don=E2=80=99t produce duplicate matches if you go that ro=
ute.</div><div><br></div><div>David J.</div><div><br></div>

--000000000000b01c5006448160b4--