This repository was archived by the owner on Feb 16, 2021. It is now read-only.
Create a MatchAgainst parser #173
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 2 commits
June 22, 2017 11:36
…in doctrine queries example usage: ``` ... WHERE MATCH_AGAINST(myContentField, :my_term 'IN NATURAL LANGUAGE MODE') > 0.3 ... ```
StijnVrolijk
force-pushed
the
match-against-extension
branch
from
09563e8 to
44967f2
Compare
carakas
approved these changes
Jun 22, 2017
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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.
Create a MatchAgainst parser which allows us to use full text search in doctrine queries
example usage: