[8.x] Fulltext index for PostgreSQL #39875
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As promised on Twitter, I want to help with the PostgreSQL support for fulltext search.
But as fulltext searching is no SQL standard, every database has an entirely different implementation. The most significant difference is that PostgreSQL fulltext searching is language-dependent because the stemming algorithms are always only designed for a specific language. Also, adding a fulltext index for multiple columns is different. The vectors for multiple columns need to be combined for the index creation. But when querying the database the exact same syntax for combining the vectors needs to be used for the query or the index will not be used. As there is no query builder method to build these conditions, I restricted the usage to a single column for the moment. With an official way to query the index the restriction could be lifted.
So the following changes had to be made:
Blueprint::fulltext()