<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Fuzzy-Search on Caktus Group</title><link>https://www.caktusgroup.com/tags/fuzzy-search/</link><description>Recent content in Fuzzy-Search on Caktus Group</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 21 Aug 2026 09:00:00 -0400</lastBuildDate><atom:link href="https://www.caktusgroup.com/tags/fuzzy-search/index.xml" rel="self" type="application/rss+xml"/><item><title>Fuzzy String Matching in Django and PostgreSQL</title><link>https://www.caktusgroup.com/blog/2026/08/21/fuzzy-string-matching-django-postgresql/</link><pubDate>Fri, 21 Aug 2026 09:00:00 -0400</pubDate><guid>https://www.caktusgroup.com/blog/2026/08/21/fuzzy-string-matching-django-postgresql/</guid><description>&lt;p>Gerald Carlton and I will be presenting on fuzzy name search at &lt;a href="https://2026.djangocon.us/talks/search-as-you-type-for-54-million-names-postgresql-django-for-fuzzy-name-matching-at-scale/" target="_blank" rel="noopener noreferrer">DjangoCon US 2026&lt;/a> on Monday, August 24, and this is the companion blog post. Searching for a person by name is harder than it looks: names might be typed differently by different operators or change over a person&amp;rsquo;s lifetime; for example, &lt;code>Smith&lt;/code> could be entered as &lt;code>Smyth&lt;/code>, &lt;code>Smythe&lt;/code>, or &lt;code>Smidt&lt;/code>, and &lt;code>Weiss&lt;/code> as &lt;code>Weiß&lt;/code>. Although names are particularly susceptible to misspelling, these strategies apply to all fuzzy string matching.&lt;/p></description></item></channel></rss>