Full-Text Search in a Database
Searching for a word inside a paragraph of text is very different from looking up an exact value like a customer ID. Full-text search is the feature that lets your users find records by typing natural words, ranked by relevance.
This article explains how it works and when a dedicated search engine is worth considering.
Why Ordinary Matching Falls Short
A simple 'contains' search is slow on large text and cannot handle word variations, typos or relevance. Searching for 'running shoe' would miss 'shoes for runners' entirely.
What Full-Text Search Adds
- Matches word stems, so 'run' finds 'running' and 'ran'.
- Ranks results by how relevant they are.
- Ignores common words and is far faster on large text.
Database vs Dedicated Search Engine
PostgreSQL and MySQL include capable full-text search that suits most sites. For very large catalogues, typo tolerance and advanced ranking, a dedicated engine such as Elasticsearch or OpenSearch may be the better fit.
Frequently Asked Questions
Can we start in the database and move later?
Yes. We often begin with built-in full-text search and introduce a dedicated engine only if your needs outgrow it.
If you need a hand with any of this, your Progressive Robot delivery team is ready to help. Raise a ticket from the Support area of your client portal or speak to your account manager and we will guide you through the next steps.