Live data from Hacker News

Show HN: PHP-fts – Full-text search engine in pure PHP, no extensions

github.com

31–35 of 35 posts

Re: Show HN: PHP-fts – Full-text search engine in pure PHP, no extensions

#33

This looks pretty solid. What's so special about the dotless Turkish i that it's ignored?

Thanks, that was a legitimate omission. I’ve now added transliteration support for Turkish-specific characters (`İ`, `ı`, `Ğ`, `Ş`, etc.) in the normalization layer.

Re: Show HN: PHP-fts – Full-text search engine in pure PHP, no extensions

#34
An alternative for PHP full text search is the PHP DuckDB client [1], and using DuckDB with the Full-Text Search extension [2]. It also stores everything on the local file system and can scale to millions of records.

[1] https://duckdb.org/docs/lts/clients/php [2] https://duckdb.org/docs/current/core_extensions/full_text_se...

Re: Show HN: PHP-fts – Full-text search engine in pure PHP, no extensions

#35

An alternative for PHP full text search is the PHP DuckDB client [1], and using DuckDB with the Full-Text Search extension [2]. It also stores everything on the local file system and can scale to millions of records. [1] https://duckdb.org/docs/lts/clients/php [2] https://duckdb.org/docs/current/core_extensions/full_text_se...

Thanks for the suggestion. DuckDB is a great tool, but it requires installing a native extension, which is exactly the scenario php-fts is designed to avoid. The primary target is shared hosting (OVH, Infomaniak, o2switch…) where you have no control over installed extensions. If you can install DuckDB, you can probably also run Meilisearch or Typesense, which are purpose-built for search.
Post reply on HN