From: | Jean Baro <jfbaro(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Phonetic representation LENGHT for DMETAPHONE, is there a way to make it longer? |
Date: | 2021-11-11 14:23:57 |
Message-ID: | CA+fQeekSmv=k=bgKtY6UXnW8x+fS-7TgQVADoPpE0AcK+UtNnw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Sorry, please remove this question, I sent it to the wrong mailing list.
On Thu, Nov 11, 2021 at 11:20 AM Jean Baro <jfbaro(at)gmail(dot)com> wrote:
> Hello people,
>
> Please, I am working on a PoC for Real-time Person Identification, and one
> of the critical aspects of it is to support both minor misspelling and
> phonetic variations of First, Middle, and Last name. Like HarinGton ==
> HarrinBton or RaphEAl == RafAEl. It's working for longer names, but it's a
> bit more imprecise for names like Lee and John. I am using Double Metaphone
> through dmetaphone() and dmetaphone_alt() in PostgreSQL 13.3 (Supabase.io).
> And although I appreciate Double Metaphone it returns a (too?) short string
> as the phonetic representation compared to metaphone(string, length).
> metaphone() has parameters to make the resulting phonetic representation
> longer. I investigated dmetaphone() and couldn't find anything other than
> the default function. Is there a way of making dmetaphone() and
> dmetaphone_alt() return a longer phonetic representation similar to
> metaphone()'s, but with a ALT variation?.
>
> Any help would be much appreciated.
>
> Thanks
>
From | Date | Subject | |
---|---|---|---|
Next Message | Laurenz Albe | 2021-11-11 16:06:36 | Re: Why in pgAdmin an active session is marked/highlighted in Red |
Previous Message | Jean Baro | 2021-11-11 14:20:19 | Phonetic representation LENGHT for DMETAPHONE, is there a way to make it longer? |