Period in query breaks query

Gagandeeps

It never will give the expected output because the search string "Twitter Starbase 1·0"  will never be converted in "Twitter Starbase 1.0". Whole text would be treated as a string including decimal character Unicode. 

PerBonomi  Bit late but it might be helpful for others also.  It seems an error with lithium match case API.  You should reach out to support. But in this case, you could query without the last two characters, it would not get you the wrong messages even where the period shows up as it would fetch those messages also. 

I performed some test here. It works fine our instance with the text string "Twitter Starbase 1.0" but not with "Twitter Database 1.0", "Twitter History 1.0" etc. (see screenshot)

1. Search Text(Twitter Database) without number

Result:  It returns the posts having text Twitter or Database or Twitter Database in the subject.

2.  Search Text(Twitter Database 1.0) with number

Result: It matches the whole text before the number.  i.e. It returns the posts having Twitter Database or Twitter Database 1.0 in the subject but never Twitter or Database individually.