search for: unmatched_quot

...ted" exception rather than letting the user think we have nothing about that subject... Would it be possible to add options to the query_parser so the user can choose if she wants a tolerant parser or not? Perhaps it could be a bitfield, something like qp.report_errors(UNMATCHED_BRACKETS | UNMATCHED_QUOTES | UNKNOWN_FIELDS | ...) with the default being no error report at all to keep intact the actual behavior (although it actually reports some errors like bad operators usage : a and and b). Your thoughts? 5. Names of operators, prefix names case sensitivity We use boolean operators a lot......