From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | Christian Marie <christian(at)ponies(dot)io> |
Cc: | PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [PATCH] RFC: Add length parameterised dmetaphone functions |
Date: | 2015-11-06 05:59:49 |
Message-ID: | CAB7nPqSnkyFhkDUE64o-1=bU42PyrQdPHt0sHoPVWChgGmWuXw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Nov 6, 2015 at 2:00 PM, Christian Marie <christian(at)ponies(dot)io> wrote:
> This patch addresses this by adding and documenting an optional argument to
> dmetaphone and dmetaphone_alt that specifies the maximum output length. This
> makes it possible to use dmetaphone on much longer inputs.
It would be good if you could register your patch here so as other
folks can track it for review, and this way we are sure that it won't
fall into the void:
https://commitfest.postgresql.org/8/
It would be good as well if you could attach a version of this patch
directly to an email sent to this thread.
> Backwards compatibility is catered for by making the new argument optional,
> defaulting to the old, hard-coded value of four. We now have:
Preserving backward-compatibility is an essential piece. Thanks.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2015-11-06 06:12:12 | Re: Beta2 Next week |
Previous Message | Michael Paquier | 2015-11-06 05:52:44 | Re: Within CF app, "Bug Fixes" should be "Bug Fixes/Refactoring" |