Re: Phonetic representation LENGHT for DMETAPHONE, is there a way to make it longer? - Mailing list pgsql-general

From Jean Baro
Subject Re: Phonetic representation LENGHT for DMETAPHONE, is there a way to make it longer?
Date
Msg-id CA+fQeekSmv=k=bgKtY6UXnW8x+fS-7TgQVADoPpE0AcK+UtNnw@mail.gmail.com
Whole thread Raw
In response to Phonetic representation LENGHT for DMETAPHONE, is there a way to make it longer?  (Jean Baro <jfbaro@gmail.com>)
List 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@gmail.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

pgsql-general by date:

Previous
From: Jean Baro
Date:
Subject: Phonetic representation LENGHT for DMETAPHONE, is there a way to make it longer?
Next
From: Laurenz Albe
Date:
Subject: Re: Why in pgAdmin an active session is marked/highlighted in Red