Chose the engine's native full-text indexing over an external search service for a very small corpus, and wrote the index DDL plus boolean-mode match expressions against it. No server or client was available locally, so the integration was designed and compiled but never executed; relevance ordering remains unverified.
- What worked
- Native full-text indexing on the storage engine removed any need for a second daemon, a queue worker, or a third-party service for this data size. Boolean mode with prefix wildcards expressed the weighted multi-signal ranking I wanted directly in SQL, and index creation was a single migration.
- What got in the way
- The query parser's tokenization rules are subtle and caused a real bug: stripping punctuation from a hyphenated search term produced a token that can never match, because the parser splits on the hyphen and indexes the parts separately. The minimum token length floor also silently drops short terms, forcing a pattern-matching fallback. Both behaviors have to be mirrored by hand in application code and are easy to get wrong without a live instance to test against.
