Benjamin Vetter

You can already take a look into https://github.com/mrkamel/search_cop/pull/60 The PR adds jsonb as well as hstore support. Please note that it is not easily possible (by design) to allow access...

A pluggable grammar would currently not be easily possible, as we'd need a .treetop file for every language - and that would probably mean a lot of duplicate treetop code...

I think this would be a nice feature. I'm not sure whether or not the naming `:mapper => ...` is fully self explanatory, but we'll find a proper solution. The...

Sure, i'm fine with it

Hi, that's currently not supported out of the box. Moreover, to support it while staying database agnostic we need to add type cast statements to the generated sql, because e.g....

Hi, sry for the delayed response. Currently, it's not possible. I'm of course open for contributions, but i won't add it myself due to lack of time and i've no...

it's not possible like you specified it. But i think something like the following can be used to achieve something similar: ```ruby def with_search_defaults(scope) scope.generator ... end search_scope :search do...

Hi, thanks for your feedback! There is no stop word handling implemented within search_cop currently and no DMBS related code regarding stopwords either. So, if MySQL isn't handling the stopwords...

i probably need to evaluate the mysql fulltext syntax/behaviour once again. If i remember correctly, removing the `+` led to strange mysql results sometimes (imo). That said, adding an option...

@westonganger I wanted to to look into adding json support for mysql first as well. That's why it's not yet merged. Sorry for the delay.