Closed dfannius closed 5 years ago
We realized after the initial commit that indexing the database by family_name
will not by itself help with substring searches. Therefore commit https://github.com/usgo/agagd/pull/54/commits/3ae525788170a87daf8f70c008275ee91d7b68a5 changes the search to an exact (case-insensitive) search on family name. This is a subset of the functionality that used to exist, but is much more functionality than not working at all. (From our vantage point, we don't know why the original functionality used to be fast on the old server.) Of course it is your call whether you want to try it out.
This is resolved in #55.
@dfannius Thank you for this patch.
Per the request at https://github.com/usgo/agagd/issues/52#issuecomment-510187439, here is a PR, with the caveats that
This change is insufficient by itself; you need to also either run a database migration or manually add the indexes for
full_name
andfamily_name
to the database.This is black-box debugging, just performed by looking at the code in the repository and observing the behavior of the website, so it's not guaranteed to fix the issue. It is the best practice anyway, though.