MIME-Version: 1.0
References: 
 <CA+fQee=8y_BB17sHg8YKyrYLe+vdBhKd2JHZjwn6b_bv2uxnjQ@mail.gmail.com>
 <773cc2b745a9cf18e9bebbdb4b32d8077c6d4ee4.camel@cybertec.at>
In-Reply-To: <773cc2b745a9cf18e9bebbdb4b32d8077c6d4ee4.camel@cybertec.at>
From: Jean Baro <jfbaro@gmail.com>
Date: Sat, 13 Nov 2021 22:06:24 -0300
Message-ID: 
 <CA+fQeekJPf+yu9+FoCfjuJGYfC2ZftNRp-Cf=zKtwLTdV3vyuw@mail.gmail.com>
Subject: Re: Phonetic representation LENGHT for DMETAPHONE, is there a way to
 make it longer?
To: Laurenz Albe <laurenz.albe@cybertec.at>
Cc: pgsql-novice@lists.postgresql.org
Content-Type: multipart/alternative; boundary="00000000000084d96705d0b5350b"
Archived-At: 
 <https://www.postgresql.org/message-id/CA%2BfQeekJPf%2Byu9%2BFoCfjuJGYfC2ZftNRp-Cf%3DzKtwLTdV3vyuw%40mail.gmail.com>
Precedence: bulk

--00000000000084d96705d0b5350b
Content-Type: text/plain; charset="UTF-8"

Thank you very much.

Em qui., 11 de nov. de 2021 13:11, Laurenz Albe <laurenz.albe@cybertec.at>
escreveu:

> On Thu, 2021-11-11 at 11:26 -0300, Jean Baro wrote:
> > 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?.
>
> These functions focus on phonetic similarity.
>
> There are no other variants of these functions, but perhaps pattern
> matching
> (which focuses on spelling, *not* phonetics) can help:
>
>   CREATE EXTENSION pg_trgm;
>
>   -- now you can use the "similar to" operator
>   SELECT * FROM tab WHERE name % 'lorenz';
>
> Yours,
> Laurenz Albe
> --
> Cybertec | https://www.cybertec-postgresql.com
>
>

--00000000000084d96705d0b5350b
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">Thank you very much.=C2=A0</div><br><div class=3D"gmail_q=
uote"><div dir=3D"ltr" class=3D"gmail_attr">Em qui., 11 de nov. de 2021 13:=
11, Laurenz Albe &lt;<a href=3D"mailto:laurenz.albe@cybertec.at">laurenz.al=
be@cybertec.at</a>&gt; escreveu:<br></div><blockquote class=3D"gmail_quote"=
 style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On=
 Thu, 2021-11-11 at 11:26 -0300, Jean Baro wrote:<br>
&gt; Please, I am working on a PoC for Real-time Person=C2=A0Identification=
, and one of the critical<br>
&gt; aspects of it is to support both minor misspelling and phonetic variat=
ions of First, Middle, and Last name.<br>
&gt; Like HarinGton =3D=3D HarrinBton or RaphEAl =3D=3D RafAEl. It&#39;s wo=
rking for longer names,<br>
&gt; but it&#39;s a bit more imprecise for names like Lee and John. I am us=
ing Double Metaphone through dmetaphone() and<br>
&gt; dmetaphone_alt() in PostgreSQL 13.3 (Supabase.io). And although I appr=
eciate Double Metaphone<br>
&gt; it returns a (too?) short string as the phonetic representation compar=
ed to metaphone(string, length).<br>
&gt; metaphone() has parameters to make the resulting phonetic representati=
on longer.<br>
&gt; I investigated dmetaphone() and couldn&#39;t find anything other than =
the default function. Is there a way of making<br>
&gt; dmetaphone() and dmetaphone_alt() return a longer phonetic representat=
ion similar to metaphone()&#39;s, but with a ALT variation?.=C2=A0<br>
<br>
These functions focus on phonetic similarity.<br>
<br>
There are no other variants of these functions, but perhaps pattern matchin=
g<br>
(which focuses on spelling, *not* phonetics) can help:<br>
<br>
=C2=A0 CREATE EXTENSION pg_trgm;<br>
<br>
=C2=A0 -- now you can use the &quot;similar to&quot; operator<br>
=C2=A0 SELECT * FROM tab WHERE name % &#39;lorenz&#39;;<br>
<br>
Yours,<br>
Laurenz Albe<br>
-- <br>
Cybertec | <a href=3D"https://www.cybertec-postgresql.com" rel=3D"noreferre=
r noreferrer" target=3D"_blank">https://www.cybertec-postgresql.com</a><br>
<br>
</blockquote></div>

--00000000000084d96705d0b5350b--