On 07/17/2012 11:38 AM, Abel Deuring wrote: > I am working currently on > https://bugs.launchpad.net/launchpad/+bug/1020443 (Full text search > broken for certain search terms having a "bad combination" of > punctuation characters, like "?!.". This a fallout bug from my previous > work on another full text search related bug: > https://bugs.launchpad.net/launchpad/+bug/29713 ) > > As explained by stub in a comment, the stored procedure ftq() does no > longer > > I see two options to fix this bug: > > (A) We can either fix the immediate problem (the fix would be quite > simple) and keep the feature "treat the characters '&|!' as logical > operators in full text searches". > > (B) Let ftq() simply remove "&|!" from queries.
I like option B because you also get to close #69628 Need to advertise "OR"/"|" operator for searches It also makes it easier to fix this bug #660283 Bug search pages should document valid search expressions PS. Maybe these bugs are fixable now #29227 Full text search only understands whitespace as a word seperator #56244 Can't search for phrases in bug reports #111956 Cannot search for identifier containing underscores -- Curtis Hovey http://launchpad.net/~sinzui
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Mailing list: https://launchpad.net/~launchpad-dev Post to : launchpad-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~launchpad-dev More help : https://help.launchpad.net/ListHelp
