Code

Opened 6 years ago

Closed 6 years ago

Last modified 3 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: master
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@…> 6 years ago.
MySQL "sounds like" (soundex) support

Download all attachments as: .zip

Change History (3)

Changed 6 years ago by dacort <django@…>

MySQL "sounds like" (soundex) support

comment:1 Changed 6 years ago by mtredinnick

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Resolution set to wontfix
  • Status changed from new to closed

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 Changed 3 years ago by orzel

  • Cc django2.20.orzelf@… added
  • Easy pickings unset
  • Severity set to Normal
  • Type set to Uncategorized
  • UI/UX unset

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.