Adding REGEXP support for block searching #40
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.
This is to evade the problem in which searching for Diamond Ore brought up Quartz Stairs.
In SQL syntax, %SEARCH_STRING%, % matches everything, even digits. Diamond ore is 56, Quartz Stairs 156
The provided example negates digits and some special symbols for quantity and after-id values to trim the results to the proper ones.
Note: This so far reduces a lot results when searching for both a keyword and a block, rarely used combination I hope.