Activity report on *[JIRA] Bug SKER4950 - AbstractESPFastSearchCommand: parsefql when term start with = characeter*
Scarab Link: http://sesat.no/scarab/issues/id/SKER4950 Module: Sesat> Kernel Activity generated by Mick Semb Wever ([EMAIL PROTECTED]) Magne Thyrhaug ([EMAIL PROTECTED]) at 12/08/2008 18:07 *Reasons for the changes* *Comments* - By Mick Semb Wever - 12/08/2008 18:13 --- "{quote}Any reason why we can't just have the query string inside "'s?{quote} There should never be a need to quote a single word|term." - By Mick Semb Wever - 12/08/2008 18:11 --- "{quote} My question is: do we have any reason for keeping .><= as word prefixes. {quote} Yes we do. From SEARCH-503 the query size:>0 must work. Here the clause's term is just ">0" (A test should definitely be written for this ;-) Instead i suggest adding these symbols to the reserved words list for the command. see getReservedWords(). The string entries in the list can be regular expressions so you can say {code}[<>=]\\w+{code} is a reserved word to be escaped. And then in escape(..) escape just these symbols. An example exists in WhiteSearchCommand.java " - By Magne Thyrhaug - 12/08/2008 18:07 --- "Any reason why we can't just have the query string inside "'s? As stated in the issue description: =oslo f*cks up, but "=oslo" seems to work."
_______________________________________________ Kernel-issues mailing list [email protected] http://sesat.no/mailman/listinfo/kernel-issues
