: > H good call, i didn't realize the escape method had been so
: > blanket in 1.3. this way we protect people who were using it in 1.3 and
: > relied on it to protect them from the legacy ";" behavior.
: Thanks hoss and ryan. That explains why the error was new to us-- we
: upgraded to
>
> : I went ahead and added it since it does not hurt anything to escape more
> : things -- it just makes the final string ugly.
>
> : In 1.3 the escape method covered everything:
>
> H good call, i didn't realize the escape method had been so
> blanket in 1.3. this way we protect people
: I went ahead and added it since it does not hurt anything to escape more
: things -- it just makes the final string ugly.
: In 1.3 the escape method covered everything:
H good call, i didn't realize the escape method had been so
blanket in 1.3. this way we protect people who were usi
On Feb 23, 2009, at 9:13 PM, Chris Hostetter wrote:
: server:/solr/select?q=field:"'anything' anything can go here\;" --
> No
: problem (but ClientUtils's escape does not escape semicolons.)
ClientUtils doesn't escape it because it's not a special character
in the
SolrQueryParser.
I w
: server:/solr/select?q=field:"'anything' anything can go here\;" --> No
: problem (but ClientUtils's escape does not escape semicolons.)
ClientUtils doesn't escape it because it's not a special character in the
SolrQueryParser.
it *is* a special character to the OldLuceneQParserPlugin if (and
server:/solr/select?q=field:"''anything can go here;" --> Lexical error,
encountered after : "\"\'\'anything can go here"
server:/solr/select?q=field:"'anything' anything can go here;" --> Same
problem
server:/solr/select?q=field:"'anything' anything can go here\;" --> No
problem (but ClientUtils
