Re: Overcoming Initcap Function limitations? - Mailing list pgsql-sql

From Steve Midgley
Subject Re: Overcoming Initcap Function limitations?
Date
Msg-id CAJexoSK3grH+4khLYMDH=dBwbZxx=F-5GUM1rzHh5fzT_GGuwg@mail.gmail.com
Whole thread Raw
In response to Re: Overcoming Initcap Function limitations?  (Greg Sabino Mullane <htamfids@gmail.com>)
Responses Re: Overcoming Initcap Function limitations?
List pgsql-sql


On Mon, Dec 4, 2023 at 10:09 AM Greg Sabino Mullane <htamfids@gmail.com> wrote:
It's not clear exactly what you are trying to achieve, but you can use Postgres' built-in text searching system to exclude stopwords. For example:

CREATE FUNCTION initcap_realword(myword TEXT)
  returns TEXT language SQL AS 
$$
SELECT CASE WHEN length(to_tsvector(myword)) < 1
  THEN myword ELSE initcap(myword) END;
$$;

You could extend that to multi-word strings with a little effort. However, knowing that macdonald should be MacDonald requires a lot more intelligence than is provided by any Postgres built-in system or extension that I know of. What you are looking at is the field of science known as Natural Language Processing, which can get very complex very quickly. But for a Postgres answer, you might combine plpython3u with spacy (https://spacy.io/usage/spacy-101).

Cheers,
Greg

I've been having some pretty good experiences with "hard" text transformations such as correct capitalization of names like MacDonald using GPT 3.5 Turbo API which is pretty cheap for the volume of data I've been working with.. Seems like Spacy might do similar things, and if it can be run locally, might be much cheaper than a rental API..

Steve

pgsql-sql by date:

Previous
From: Greg Sabino Mullane
Date:
Subject: Re: Overcoming Initcap Function limitations?
Next
From: Bo Guo
Date:
Subject: Re: Overcoming Initcap Function limitations?