| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Vincent Veyron <vv(dot)lists(at)wanadoo(dot)fr> |
| Cc: | Rich Shepard <rshepard(at)appl-ecosys(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Selecting all variations of job title in a list |
| Date: | 2025-11-26 15:52:03 |
| Message-ID: | CAKFQuwY2W1WB2qnMuhJ7=GD_rgNmm+N=a7_ZHEtuudw=qajJwg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wednesday, November 26, 2025, Vincent Veyron <vv(dot)lists(at)wanadoo(dot)fr> wrote:
> On Wed, 26 Nov 2025 07:10:16 -0800 (PST)
> Rich Shepard <rshepard(at)appl-ecosys(dot)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.
Keep in mind the native flavor of regex in PostgreSQL is TCL, not Perl.
But I’d still say regexp is not the best solution here - unless you
encapsulate the logic in a function. I suspect you’ll 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’t produce duplicate
matches if you go that route.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rich Shepard | 2025-11-26 16:08:55 | Re: Selecting all variations of job title in a list |
| Previous Message | Vincent Veyron | 2025-11-26 15:43:56 | Re: Selecting all variations of job title in a list |