Queries are created by iterating a query objects properties, where a query of { foo:a, bar:b } becomes a parameter of 'query=foo:a+bar:b'. This appears to result in an OR operation where records matching either condition are returned.
We wish to do an AND, which would need a lucene query of 'query=foo:a AND bar:b'. Using the RavenDB http API directly, we are able to get the desired results by supplying the encoded query as 'query=foo%3Aa%20AND%20bar%3Ab'. As an aside, 'query=foo:a%20AND%20bar:b' also works.
We also have a requirement for searching lucene date ranges, e.g. '[2013-02-25T00:30:45.7590116Z TO NULL] '. Again, supplying an encoded query to the http API gets the desired result.
Do you provide support for various combinations of boolean operators and date ranges, or do you have any plans to do so in the future?
Queries are created by iterating a query objects properties, where a query of { foo:a, bar:b } becomes a parameter of 'query=foo:a+bar:b'. This appears to result in an OR operation where records matching either condition are returned.
We wish to do an AND, which would need a lucene query of 'query=foo:a AND bar:b'. Using the RavenDB http API directly, we are able to get the desired results by supplying the encoded query as 'query=foo%3Aa%20AND%20bar%3Ab'. As an aside, 'query=foo:a%20AND%20bar:b' also works.
We also have a requirement for searching lucene date ranges, e.g. '[2013-02-25T00:30:45.7590116Z TO NULL] '. Again, supplying an encoded query to the http API gets the desired result.
Do you provide support for various combinations of boolean operators and date ranges, or do you have any plans to do so in the future?