From: | Greg Sabino Mullane <htamfids(at)gmail(dot)com> |
---|---|
To: | Bo Guo <bo(dot)guo(at)gisticinc(dot)com> |
Cc: | pgsql-sql(at)lists(dot)postgresql(dot)org |
Subject: | Re: Overcoming Initcap Function limitations? |
Date: | 2023-12-04 18:08:03 |
Message-ID: | CAKAnmmKhepxPzLWiU2JMNWsNiwLmQAyKCgV-f2dMot1hKVa-hA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Steve Midgley | 2023-12-04 18:39:12 | Re: Overcoming Initcap Function limitations? |
Previous Message | Bo Guo | 2023-12-02 19:03:45 | Overcoming Initcap Function limitations? |