Bug #28624 Improving FULL-TEXT index and searching
Submitted: 23 May 2007 16:36 Modified: 22 Feb 2013 16:44
Reporter: Miguel Velilla meucat Email Updates:
Status: Verified Impact on me:
Category:MySQL Server: FULLTEXT search Severity:S4 (Feature request)
Version:5.0 OS:Any (Bit to bit search for matching against '*needle*' (as %like% does) )
Assigned to: CPU Architecture:Any
Tags: match full-text

[23 May 2007 16:36] Miguel Velilla meucat
TO: MySql Development Team
COMMAND: Full-Text Search Index & MATCH .. AGAINST commands
SUBJECT: Suggestion for a 'true' full-text search command equal to '%like%' or INSTRING commands.
Hello Sirs
Many database developers need a 'true' full-text search ability to solve queries. I mean 'true' search when you query for 'tabas' and a record containing 'database' is retrieved.
I suppose current MySql Full-Text index proceeds by first splitting text into single words, then indexing isolated words and automatically pointing every word to its related register, so this the reason you only made prefixed wildcards ('datab*') but not postfixed wildcards ('*tabase') when matching strings. I suppose this is because postfixed wildcards are impossible to manage with current indexing methods.
In this post, I would like suggest to you a shortcut to solve this task, since it is impossible to solve it through normal indexing. This shortcut could improve time and performance by 3 to 4 orders of magnitude over 'brute force' as happen with '%like%' and INSTRING commands.

How to repeat:
match (field) against ('*needle*')
[22 Feb 2013 16:44] Sveta Smirnova
Thank you for the feature request.

Currently you can write full text plugin doing so.