carlson@bookandhammer.com writes: When I wrote the mail asking about formatting queries, I didn't mention why I needed to search using &, and =. If you haven't guessed it, I needed to for search for URL:s. Since this need can't be that uncommon, I think Peters suggestion would be well worth implementing. /Stefan Bergstrand > Hi, > > In looking into the QueryParser, I noticed that most charcters where > allowed in the queryString buyt quite a few common characters where > not. > Can we look to update this to allow more characters? > Obviously this is a big change since it will affect the way all tokens > are made. > > I would suggest adding "/&=#\" > Also, I think that we should add "." as a term_start_char. This > handles names like .NET, .com ... > > > Any thoughts on this? > > --Peter > > > On Monday, January 14, 2002, at 12:12 AM, Brian Goetz wrote: > > How do I format the query in order to keep the parser satisfied? I > have tried the usual \-escaping of difficult characters, but that > doesn't work either. Is there a way to set which characters are > allowed in a query or something similar? > > Right now, the parser doesn't know what to do with the characters like > = and &. > > > -- > To unsubscribe, e-mail: unsubscribe@jakarta.apache.org> > For additional commands, e-mail: help@jakarta.apache.org> -- To unsubscribe, e-mail: For additional commands, e-mail: