I will second Rick's approach and have implemented something very
similar for a client when soundex feel short of expectation. It
worked very well.
On Mon, Jun 3, 2013 at 5:43 PM, Rick James wrote:
> Soundex is the 'right' approach, but it needs improvement. So, find an
> improvement, then do
Soundex is the 'right' approach, but it needs improvement. So, find an
improvement, then do something like this...
Store the Soundex value in a column of its own, INDEX that column, and JOIN on
that column using "=". Thus, ...
* You have spent the effort to convert to Soundex once, not on every
On 03.06.2013 17:29, h...@tbbs.net wrote:
> I wish to join two tables on likeness, not equality, of character strings.
> Soundex does not work. I am using the Levenstein edit distance, written in
> SQL, a very costly test, and I am in no position to write it in C and link it
> to MySQL--and join
- Original Message -
> From: h...@tbbs.net
>
> I wish to join two tables on likeness, not equality, of character
> strings. Soundex does not work. I am using the Levenstein edit
> distance, written in SQL, a very costly test, and I am in no
> position to write it in C and link it to MySQL-
I wish to join two tables on likeness, not equality, of character strings.
Soundex does not work. I am using the Levenstein edit distance, written in SQL,
a very costly test, and I am in no position to write it in C and link it to
MySQL--and joining on equality takes a fraction of a second, and
For more information, see http://www.upscene.com/go/?go=hopper
This release contains bugfixes and improvements, see
http://www.upscene.com/go/?go=news&id=20130603
Bugfixes include, but not limited to:
- possible "data type not supported" on specific (param) IS NULL constructor
