postgresql/contrib/fuzzystrmatch/Makefile

# $Header: /cvsroot/pgsql/contrib/fuzzystrmatch/Makefile,v 1.2 2001/09/06 10:49:29 petere Exp $

subdir = contrib/fuzzystrmatch
top_builddir = ../..
include $(top_builddir)/src/Makefile.global

MODULES = fuzzystrmatch
DATA_built = fuzzystrmatch.sql
DOCS = README.fuzzystrmatch README.soundex

include $(top_srcdir)/contrib/contrib-global.mk
To fix the perpetually broken makefiles in the contrib tree, I have written a generic framework of rules that the contrib makefiles can use instead of writing their own each time. You only need to set a few variables and off you go. 2001-09-06 18:49:30 +08:00			`# $Header: /cvsroot/pgsql/contrib/fuzzystrmatch/Makefile,v 1.2 2001/09/06 10:49:29 petere Exp $`

Per this discussion, here's a patch to implement both levenshtein() and metaphone() in a contrib. There seem to be a fair number of different approaches to both of these algorithms. I used the simplest case for levenshtein which has a cost of 1 for any character insertion, deletion, or substitution. For metaphone, I adapted the same code from CPAN that the PHP folks did. A couple of questions: 1. Does it make sense to fold the soundex contrib together with this one? 2. I was debating trying to add multibyte support to levenshtein (it would make no sense at all for metaphone), but a quick search through the contrib directory found no hits on the word MULTIBYTE. Should worry about adding multibyte support to levenshtein()? Joe Conway 2001-08-08 00:47:43 +08:00			`subdir = contrib/fuzzystrmatch`
			`top_builddir = ../..`
			`include $(top_builddir)/src/Makefile.global`

To fix the perpetually broken makefiles in the contrib tree, I have written a generic framework of rules that the contrib makefiles can use instead of writing their own each time. You only need to set a few variables and off you go. 2001-09-06 18:49:30 +08:00			`MODULES = fuzzystrmatch`
			`DATA_built = fuzzystrmatch.sql`
			`DOCS = README.fuzzystrmatch README.soundex`
Per this discussion, here's a patch to implement both levenshtein() and metaphone() in a contrib. There seem to be a fair number of different approaches to both of these algorithms. I used the simplest case for levenshtein which has a cost of 1 for any character insertion, deletion, or substitution. For metaphone, I adapted the same code from CPAN that the PHP folks did. A couple of questions: 1. Does it make sense to fold the soundex contrib together with this one? 2. I was debating trying to add multibyte support to levenshtein (it would make no sense at all for metaphone), but a quick search through the contrib directory found no hits on the word MULTIBYTE. Should worry about adding multibyte support to levenshtein()? Joe Conway 2001-08-08 00:47:43 +08:00
To fix the perpetually broken makefiles in the contrib tree, I have written a generic framework of rules that the contrib makefiles can use instead of writing their own each time. You only need to set a few variables and off you go. 2001-09-06 18:49:30 +08:00			`include $(top_srcdir)/contrib/contrib-global.mk`