The query language is NOT pure boolean. Hoss wrote this up: http://searchhub.org/2011/12/28/why-not-and-or-and-not/
Best Erick On Mon, Apr 15, 2013 at 12:54 PM, Roman Chyla <roman.ch...@gmail.com> wrote: > Oh, sorry, I have assumed lucene query parser. I think SOLR qp must be > different then, because for me it works as expected (our qp parser is > identical with lucene in the way it treats modifiers +/- and operators > AND/OR/NOT -- NOT must be joining two clauses: a NOT b, the first cannot be > negative, as Chris points out; the modifier however can be first - but it > cannot be alone, there must be at least one positive clause). Otherwise, > -field:x it is changed into field:x > > http://labs.adsabs.harvard.edu/adsabs/search/?q=%28*+-abstract%3Ablack%29+AND+abstract%3Ahole*&db_key=ASTRONOMY&sort_type=DATE > http://labs.adsabs.harvard.edu/adsabs/search/?q=%28-abstract%3Ablack%29+AND+abstract%3Ahole*&db_key=ASTRONOMY&sort_type=DATE > > roman > > > On Mon, Apr 15, 2013 at 12:25 PM, Peter Schütt <newsgro...@pstt.de> wrote: > >> Hallo, >> >> >> Roman Chyla <roman.ch...@gmail.com> wrote in >> news:caen8dywjrl+e3b0hpc9ntlmjtrkasrqlvkzhkqxopmlhhfn...@mail.gmail.com: >> >> > should be: -city:H* OR zip:30* >> > >> -city:H* OR zip:30* numFound:2520 >> >> gives the same wrong result. >> >> >> Another Idea? >> >> Ciao >> Peter Schütt >> >> >>
