About

I just wanted to learn about native search features in SQLite and I accidentally built a website.

Search

The search demo on the releases page uses The FTS5 SQLite extension with trigram tokenization for substring matching, so partial search terms like "que" will return results for "queen" while "queen's" returns no results. Proper FTS search can also be used but there are tradeoffs so the right choice depends on the application. Either option is a convenient starting point for implementing search with minimal complexity. For cases where native PostgreSQL features don't meet the requirements, there are plenty of established search patterns and solutions available.

Compare this demo to the same app using PostgreSQL FTS

HTMX

HTMX is used in the search demo for partial client-side re-rendering of search results and pagination. There's no build required, it's just a tiny static js file that's only loaded on the releases page. All the client-side functionality it provides in the demo is based on a few html attributes. Check out the htmx website to learn more.