Added test for using MatchAgainst in where clause #419
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.
I have added a unit test to show that the current MatchAgainst does not work in a where clause. I think the reason is that the DQL parser thinks it is a simple conditional expression and expects an operator after the
AGAINST(...)
token.One can workaround this by adding
> 0
to the condition:I do not know if this should or can be fixed. But if not, it would be good to add a note somewhere. I can do that if I get a hint where to place it.