Fix: Escape MySQL wildcards (%) and (_) in search queries #815
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.
Problem
When searching for values containing MySQL wildcards (
%
and_
), these characters are interpreted as wildcard patterns rather than literal characters, resulting in incorrect query results.Solution
addcslashes()
to escape%
and_
in search terms before they are used inLIKE
orILIKE
queries.Testing
%
or_
return accurate results without unintended wildcard behavior.Contribution
This change adheres to the PSR-2 coding standards and follows the contribution guidelines outlined in the repository.
Fixes #814