Near Text Search

[Peter Haworth]

You don't need another column.

If you don't get an exact match

SELECT soundex(name)=soundex("Wittier Fun Center")

Not sure of performance implications.

Pete
lcSQL Software
On Feb 26, 2014 8:12 PM, "Bob Sneidar" <bobsneidar at iotecdigital.com> wrote:

> I just did a query on soundex for 3 values: Whittier Fun Center, Whitier
> Fun Center and Wittier Fun Center. All returned the same result. I think
> what I will do is create a column populated with the soundex of the
> customer name as a secondary lookup when I don't get an exact match, then
> alert the user and ask him if this isn't really what he wanted.
>
> Bob
>
>
> On Feb 26, 2014, at 19:38 , Richard Gaskin <ambassador at fourthworld.com>
> wrote:
>
> > I'm still missing it - where can one find Devin's Levenstein function?
> >
> >
> > Bob Sneidar:
> >> Don't know how I missed that, thanks.
> >>
> >> On Feb 26, 2014, at 18:50 , Peter Haworth wrote:
> >>
> >>>
> >>> If I remember correctly, Devin has some functions that implement a
> >>> Levenstein Distance algorithm which will identify potential
> misspellings of
> >>> a word
> >
> >
> > _______________________________________________
> > use-livecode mailing list
> > use-livecode at lists.runrev.com
> > Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> > http://lists.runrev.com/mailman/listinfo/use-livecode
>
>
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>