| From: | Bryan Sayer <blslists(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Selecting all variations of job title in a list |
| Date: | 2025-11-26 17:01:46 |
| Message-ID: | c9a9dedb-4a84-49d3-afac-f134ffd62f79@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
I am not very skilled at Postgresql specifically, but when I was doing
SQL in another environment I would just do
select distinct (or unique) jobtitle
usually getting a count of how many times each title occurred. Then I
would create a mapping to standardize the the job titles.
*Bryan Sayer*
Retired Demographer/Statistician
/In a world in which you can be anything, *be kind*/
On 11/26/2025 11:10 AM, Rich Shepard wrote:
> 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 | Adrian Klaver | 2025-11-26 19:26:45 | Re: Wal streaming |
| Previous Message | Ron Johnson | 2025-11-26 16:47:38 | Re: Question on PostgreSQL Table Partitioning – Performance of Queries That Do Not Use the Partition Key |