Turns a user query like 'georgia -(atlanta or decatur)' into 'georgia AND NOT (atlanta or decatur)
Allows developers to provide a boolean search query interface, similar to Google or Sphinx search or other full-text search (FTS) engines.
Turns a user query like '
georgia -(atlanta or decatur)' into '
georgia AND NOT (atlanta or decatur)' which is then turned into the follow SQL:
"ip", /* ip address */
"visits", /* how many requests they've made */
/* A table similar to apaches access log. See my extension yii2-ipFilter */
("visitor"."ip" ILIKE '%georgia%')
OR ("visitor"."city" ILIKE '%georgia%')
OR ("visitor"."region" ILIKE '%georgia%')
AND ( /** marvel as we efortlessly generate a subquery */
"ip" NOT IN (
("visitor"."ip" ILIKE '%atlanta%')
OR ("visitor"."city" ILIKE '%atlanta%')
OR ("visitor"."region" ILIKE '%atlanta%')
("visitor"."ip" ILIKE '%decatur%')
OR ("visitor"."city" ILIKE '%decatur%')
OR ("visitor"."region" ILIKE '%decatur%')
The preferred way to install this extension is through composer.
php composer.phar require --prefer-dist johnsnook/yii2-parsel "*"
to the require section of your
"Look, I didn't know I could speak Parseltongue! What else don't I know about myself? Look. Maybe you can do something, even something horrible and not know you did it."
Once the extension is installed, simply use it in your code by :
$userQuery = 'good AND plenty -licorice';
$parsel = new ParselQuery([
'userQuery' => $this->userQuery,
'dbQuery' => Script::find()
Fields to be search must be either text, varchar or char currently. Future versions may expand to number, dates and maybe even JSON. All search terms, except where specified bye the full match operator are wrapped in your databases wildcard of choice. Searching for "smart" is equivalent to the SQL expression
'%smart%'. Search is case insensitive as long as your database's
LIKE operator is. PostgreSQL will use
'AND' is the default behavior. "smart pretty" is the same as "smart AND pretty."
'OR' allows more results in your query: "smart OR pretty."
|-||Negation||The user query "smart pretty -judgmental" parses to "smart AND pretty AND NOT judgmental"|
|()||Sub-query||Allows grouping of terms . The user query "-crazy (smart AND pretty)" parses to "NOT crazy AND (smart AND pretty)"|
|*||Wildcard||Fuzzy matches. "butt*" matches butt, buttery, buttered etc.|
|_||Character wildcard||Matches one character. "boo_" matches boot, book, bool, boon, etc.|
|=||Full match||Entire fields must be equal to the term. "=georgia" only matches where one or more fields is exactly equal to the search term. The search term will NOT be bracketed with %, but wildcards can still be used.|
|""||Double quotes||Phrase. '"Super fun"' searches for the full phrase, space include. Wild cards, negation and exact match operators all work within the phrase.|
|''||Single quotes||Phrase, no wildcards. The term will not be evaluated for * or _, but will be wrapped in wildcards. If a % or _ is in the term, it will be escaped. 'P%on*' becomes '%P\%on*%'.|
|:||Field||Specify the field to search. 'name:jo*' will search the name field for 'jo*.' If no field name matches, all fields will be searched for 'name:jo*'|
See files in /examples. If it's still up, you might also be able to play with an example here
This project was built by heavily modifying the excellent "Search Query Parser" project. I de-abstracted the token structure and modified the parser class to better fit my needs. Their licsence file should be found at the root of this project.