Opened 16 years ago

Closed 16 years ago

Last modified 13 years ago

#8553 closed Uncategorized (wontfix)

Add soundex support to MySQL (and others)

Reported by: dacort <django@…> Owned by: nobody
Component: Database layer (models, ORM) Version: dev
Severity: Normal Keywords: mysql, soundex
Cc: django2.20.orzelf@… Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

I needed to use MySQL sounds like support in an app recently and found it to be seemingly easy to add support for this. Not sure what the policy is about database-specific calls, but at least both postgres, sqlite, and oracle all appear to support some form of soundex.

http://www.postgresql.org/docs/8.3/static/fuzzystrmatch.html
http://www.sqlite.org/lang_corefunc.html
http://www.techonthenet.com/oracle/functions/soundex.php

I've attached my changes for MySQL.

Attachments (1)

mysql_soundslike.diff (1.7 KB ) - added by dacort <django@…> 16 years ago.
MySQL "sounds like" (soundex) support

Download all attachments as: .zip

Change History (3)

by dacort <django@…>, 16 years ago

Attachment: mysql_soundslike.diff added

MySQL "sounds like" (soundex) support

comment:1 by Malcolm Tredinnick, 16 years ago

Resolution: wontfix
Status: newclosed

Not really worth it. Soundex support has enough collisions that it's often preferable to use other, similar algorithms. So then it becomes a question of which versions to include. Since adding extra lookup types is actually possible by subclassing the Query class (django.contrib.gis already does this), no modifications to core should be needed for this.

comment:2 by Thomas Capricelli, 13 years ago

Cc: django2.20.orzelf@… added
Easy pickings: unset
Severity: Normal
Type: Uncategorized
UI/UX: unset
Note: See TracTickets for help on using tickets.
Back to Top