[Forwardport] FIX for issue#14855 - Adding an * to do a customer search #15077
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
…T values shoud be stripped of special chars if they are not intended to be used https://dev.mysql.com/doc/refman/5.5/en/fulltext-search.html Searching "*" in any grid list causes a 400 error because of no filtering is applied.
magento-engcom-team
added
Release Line: 2.3
Partner: Interactiv4
magento-engcom-team
pushed a commit
that referenced
this pull request
May 12, 2018
Contributor
|
Hi @adrian-martinez-interactiv4. Thank you for your contribution. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
Original Pull Request
#14905
According to MySQL fulltext documentation, AGAINST values shoud be stripped of special chars if they are not intended to be used.
https://dev.mysql.com/doc/refman/5.5/en/fulltext-search.html
Searching "*" in any grid list causes a 400 error because of no filtering is applied.
Fixed Issues (if relevant)
Contribution checklist