> > : 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: > > Hmmmm.... 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 trunk from 1.3 release and this exception came from a solrj processed query that used to work.
