Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mlAzI-0003a7-KQ for pgsql-novice@arkaria.postgresql.org; Thu, 11 Nov 2021 14:23:36 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mlAzH-0007i5-IN for pgsql-novice@arkaria.postgresql.org; Thu, 11 Nov 2021 14:23:35 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mlAzH-0007hq-9t for pgsql-novice@lists.postgresql.org; Thu, 11 Nov 2021 14:23:35 +0000 Received: from mail-io1-xd34.google.com ([2607:f8b0:4864:20::d34]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1mlAzF-000057-9X for pgsql-novice@postgresql.org; Thu, 11 Nov 2021 14:23:34 +0000 Received: by mail-io1-xd34.google.com with SMTP id x10so7108984ioj.9 for ; Thu, 11 Nov 2021 06:23:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:from:date:message-id:subject:to; bh=NeUcrZfhOJ0X1WzidB/vPI8C0NJ+Usz71k8K3PwihOw=; b=ohOa3iFk5r6bot+Mvhg0Cc7Fkv6IgKeOEVdk5o4eg+KIm5R+zwnirVc4pomnClVTUG Jgdq0rbUCkiPdENgZKV4jxHPz1CKpWONPL/JMcbkgSI5WmoPE5/IA2HmVWkzI/YNcTgh YloQ8UCGWfXVeZCWqG5v+9K4CZBoFZEDMVJoR+D8/TNLsfcOtvwjafbWvcXZVLhB7f4x g525VdBLUjJLwyaAbTHohUkRq87npzm+EFZ2FNxOi+UdX3ULgkUPv02fKXyxwunsjIOR l6cKjIC8v4DvZ3Kn2fICaafoYTTRHSvSnMvNoZAGg34GyIQWOstABVMQPKGDOebtdm4n wY6Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=NeUcrZfhOJ0X1WzidB/vPI8C0NJ+Usz71k8K3PwihOw=; b=OH7pr47Ck36USvJg83CxpPDFfKL4WkwRLHKXHWKddmd9kZeYHDiQx1x6rPrNM91f0/ Iz0cjvvCnF7kHQDkodKpxlAC82UQ9LjzTfS5Oa4KLA8eUnBHXBlLmJQ9jtAx8toD8h8m /7+CHojT89m7Bj7fy+A/r7KwMhoLIj+qXk8EXd6TK7DtuSXR32wpEYVh4SbFX3kIEbqv qVGY/nTKHWBKCQoOmxAYCn+/yIVu5nOomHYG+AUzbcfmwXhy+QTuY0V3bKnRQUyagkj5 +YTj1rFpd1TT7WS8TAg5G8JTFSsYZOEHpAvg6lJbBdTiyTKh6buuguy/Oza7R752vkvE yppQ== X-Gm-Message-State: AOAM5320p/x/Yqg1QDoaH5GbgEcvb1MjEoTLXIPeMbQnHly8nNN+ski8 W+Qn6zDimIrRs3hAauxPEOfZGx58lkm5/gFAEZ+C90ApWn+w451Q X-Google-Smtp-Source: ABdhPJxzaGZG94KfVmNLlaUCf7X+qcGBZN+g408yoNPdNK1L4+aWemZ09gprlwl/VFycP7bTbA8ANx4ccKMyJmiyFSI= X-Received: by 2002:a6b:bc43:: with SMTP id m64mr5123153iof.141.1636640612207; Thu, 11 Nov 2021 06:23:32 -0800 (PST) MIME-Version: 1.0 From: Jean Baro Date: Thu, 11 Nov 2021 11:23:21 -0300 Message-ID: Subject: Phonetic representation LENGHT for DMETAPHONE, is there a way to make it longer? To: pgsql-novice@postgresql.org Content-Type: multipart/alternative; boundary="00000000000050d0bb05d08416dc" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000050d0bb05d08416dc Content-Type: text/plain; charset="UTF-8" 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 --00000000000050d0bb05d08416dc Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Hello people,=C2=A0

Please, I am working on a= PoC for Real-time Person=C2=A0Identification, and one of the critical aspe= cts of it is to support both minor misspelling and phonetic variations of F= irst, Middle, and Last name. Like HarinGton =3D=3D HarrinBton or RaphEAl = =3D=3D RafAEl. It's working for longer names, but it's a bit more i= mprecise for names like Lee and John. I am using Double Metaphone through d= metaphone() and dmetaphone_alt() in PostgreSQL 13.3 (Supabase.io). And alth= ough 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 inve= stigated dmetaphone() and couldn't find anything other than the default= function. Is there a way of making dmetaphone() and dmetaphone_alt() retur= n a longer phonetic representation similar to metaphone()'s, but with a= ALT variation?.=C2=A0

Any help would be much appreciated.=C2=A0

Thanks

--00000000000050d0bb05d08416dc--