Hello Chris, Thanks for the reply. And sorry for sounding impatient - I've been working in the weekend and I wasn't sure if I expressed my question well, hence why the second email :)
I understand I can url-encode the space. My question, which I failed to mention in my first email, is that, what if the search term in fq also has a space in it? Quoting with " " does not seem to be a solution because quotes may appear in the query as well? fq=+name:jack smith +section:0 BTW, space is sometimes encoded as %20, sometimes as "+". So, solr expects %20 in this case? Or both are fine? -- Best regards, Jack Saturday, May 5, 2007, 6:43:23 PM, you wrote: > first off, please have a little patience when sending mai lto the mailing > list ... 17 hours between "reposting" isn't relaly a lot ... especially on > a weekend, when many people are out of hte country for a confrence, and > i'm sick :) > On to your question... > : fq=+popularity:[10 TO *] +section:0 > : is equivalent to > : fq=popularity:[10 TO *]&fq=section:0 > : But is the first line a valid URL with the space before the +? > it's not really valid in the "meets the RFC" sense, it's mainly for > illustrative purposes ... you could type that into your browser and it > would probably work, but to be more strict we should be explicit... > fq=%2Bpopularity:[10%20TO%20*]%20%2Bsection:0 > is equivalent to > fq=popularity:[10%20TO%20*]&fq=section:0 > ... but isn't the version o nthe wiki a bit more readable? > : The problem with the second line is that fq shows up multiple times. > : In the web framework I am using, URL arguments are parsed and > : converted into a dictionary and only the last value is used. > i'm not sure what do tell you about that, other then that it sounds > like your web framework sucks. multi valued params are extremely common, > and i can't imagine a web framework not supporting them. > -Hoss
