Benjamin Vetter

I've added this feature in branch 23_fulltext_right_wildcard. You're very welcome to try it out already.

Hi, thx for your feedback. So, in essence you ask for what elasticsearch calls the "default_operator": https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-query-string-query.html Currently, search_cop always uses AND as default operator, such that if you search...

Sure, it starts in the treetop grammer. More specifically, in `rule and_expression` spaces are interpreted as AND operators. We need to change `` within ``` ... / space !('OR' /...

ok, thx, i'll look into it.

i'm not quite sure i want to add support for a database specific datatype, that needs to be explicity enabled (postgres module). You can easily get the same (search-wise) via...

ok, well, then we probably need to define datatype aliases/mappings or some kind of plugin architecture, such that the main code base stays clean. However, the benefit of adding support...

You can search for empty strings via `email=""` and `NOT email=""`. You are however not able search for `NULL` values. Regarding your examples, i'd favor `exists:[field]`.

Hi @MadBomber and thanks for reporting! You are right. That's an error in the README. ```ruby Book.search("created_at:2014").to_sql # ... (books.created_at >= '2013-12-31 23:00:00' AND \"books\".\"created_at\"

Please note that the concrete values are of course dependent on your time zone settings

Thanks for the PR! It's already merged. Moreover, thanks for suggesting this new section. I'll use it if i may and keep this issue open until integrated.