From: | Marco Pennekamp <marco(dot)pennekamp96(at)gmail(dot)com> |
---|---|
To: | Marko Tiikkaja <marko(at)joh(dot)to> |
Cc: | pgsql-docs <pgsql-docs(at)postgresql(dot)org> |
Subject: | Re: Levenshtein function cost parameters are in the wrong order |
Date: | 2017-10-03 12:41:42 |
Message-ID: | CAO+D04XA_5mg=EwD5XKkEhqoDqrBmA5MjdR5xYso6hbt-EgxSw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
Oh, yeah. I didn't think about the source/target order! Thank you for
checking and sorry for the inconvenience!
On Tue, Oct 3, 2017 at 2:34 PM Marko Tiikkaja <marko(at)joh(dot)to> wrote:
> On Mon, Oct 2, 2017 at 5:37 PM, <marco(dot)pennekamp96(at)gmail(dot)com> wrote:
>
>> The following documentation comment has been logged on the website:
>>
>> Page: https://www.postgresql.org/docs/9.6/static/fuzzystrmatch.html
>> Description:
>>
>> The fuzzystrmatch documentation says that the order for the Levenshtein
>> cost
>> parameters is insertion, deletion, substitution. Based on my tests with
>> Postgres 9.4, the order should be deletion, insertion, substitution, since
>> the algorithm behaves that way (this can be easily checked).
>
>
> I did check, and they seem correct to me:
>
> =# select levenshtein('aaa', 'aaab', 1, 100, 100);
> levenshtein
> -------------
> 1
> (1 row)
>
> Notice that the order of the first two arguments is (source, target).
>
>
> .m
>
From | Date | Subject | |
---|---|---|---|
Next Message | Euler Taveira | 2017-10-03 13:13:23 | Re: Doc BUG and/or Change Request: Include Postgres's system columns in reserved words in docs, Chnage to previx sytem colums with 2 underscores? |
Previous Message | Marko Tiikkaja | 2017-10-03 12:34:31 | Re: Levenshtein function cost parameters are in the wrong order |