| From: | Rich Shepard <rshepard(at)appl-ecosys(dot)com> |
|---|---|
| To: | |
| Cc: | "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 16:10:54 |
| Message-ID: | 989b6fd-2979-8ac6-13b-3916d2e47de8@appl-ecosys.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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’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,
Thanks,
Rich
| From | Date | Subject | |
|---|---|---|---|
| Next Message | atma ram | 2025-11-26 16:29:22 | Re: Question on PostgreSQL Table Partitioning – Performance of Queries That Do Not Use the Partition Key |
| Previous Message | Rich Shepard | 2025-11-26 16:08:55 | Re: Selecting all variations of job title in a list |