Bug write-up: search found nothing for hyphenated values (#102) searchParseQuery() DELETED punctuation and glued what remained together, so "05145-8841815" was searched for as the single word "051458841815". MySQL had split the value on the hyphen and indexed two words, so the glued version existed nowhere. The page leads on why the reporter's table looked inconsistent: a comma and a full stop worked while a hyphen did not, because the strip list is the MySQL boolean operators and a comma is not one of them. Those two survived into the query and MySQL split there itself - accidentally doing the right thing. Also records that the file already contained the fix nine lines above: the quoted-phrase branch substitutes a SPACE where the word branch substituted the empty string, which is why "05145-8841815" in quotes worked all along. Names the two cases that are NOT fixed and why they cannot be without changing the index engine - and corrects the report's framing of one: a "latter part" that is a whole word does work (789 finds GHI-789); it only fails inside a single word. Verification includes a real Excel file emailed in as TICKET-000108, searched through the real query path, with a two-hyphen value to prove three-way splits. Adds the Bugs-Resolved row.