Re: soundex and metaphone - Mailing list pgsql-hackers

From Jonah H. Harris
Subject Re: soundex and metaphone
Date
Msg-id 4295CA16.2020608@tvi.edu
Whole thread Raw
In response to Re: soundex and metaphone  (Douglas McNaught <doug@mcnaught.org>)
Responses Re: soundex and metaphone  (Peter Eisentraut <peter_e@gmx.net>)
Re: soundex and metaphone  (Andrew Dunstan <andrew@dunslane.net>)
Re: soundex and metaphone  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: soundex and metaphone  (Ron Mayer <rm_pg@cheapcomplexdevices.com>)
List pgsql-hackers
At a minimum I think we should support soundex in the core.  I'm willing 
to move soundex and metaphone into the backend.  Does anyone see a 
reason not to do so?

Douglas McNaught wrote:

>"Jonah H. Harris" <jharris@tvi.edu> writes:
>
>  
>
>>Hey everyone,
>>
>>I've been working with a couple people who didn't know that soundex
>>and metaphone were included in the distribution as contrib modules.
>>While it's their fault that they didn't check contrib, soundex is
>>pretty common among database systems and I was wondering if there was
>>a reason it is not included as a core function?
>>    
>>
>
>Because no one's taken ownership of the code and made a case for
>integrating it into the core backend.
>
>-Doug
>
>---------------------------(end of broadcast)---------------------------
>TIP 9: the planner will ignore your desire to choose an index scan if your
>      joining column's datatypes do not match
>  
>



pgsql-hackers by date:

Previous
From: Douglas McNaught
Date:
Subject: Re: soundex and metaphone
Next
From: Stephan Szabo
Date:
Subject: Re: foreign keys and RI triggers