@oliverroick apologies for the delay in reviewing the search PR (#58). This PR resolves the merge conflicts in the search branch and includes a small change to limit results and add case insensitivity. The search implementation looks solid, and if I haven't introduced any errors, both PRs should be good to merge.
There is one issue I believe we should track in #51 and address separately: adding support for proximity search to handle misspellings, name variations, and names in other languages (e.g., non-English names like São Paulo, München, etc.). There is a PostgreSQL extension that might help us make search work on these cases, but it is not enable in the database at the moment.
@oliverroick apologies for the delay in reviewing the search PR (#58). This PR resolves the merge conflicts in the
searchbranch and includes a small change to limit results and add case insensitivity. The search implementation looks solid, and if I haven't introduced any errors, both PRs should be good to merge.There is one issue I believe we should track in #51 and address separately: adding support for proximity search to handle misspellings, name variations, and names in other languages (e.g., non-English names like São Paulo, München, etc.). There is a PostgreSQL extension that might help us make search work on these cases, but it is not enable in the database at the moment.