Full-Text Restrictions 12.10.5 Full-Text Restrictions 12.10.6 Fine-Tuning MySQL Full-Text Search 2218 Full-text search is carefully tuned for effectiveness. Modifying the default behavior in most cases can actually decrease effectiveness.  Do not alter the MySQL sources unless you know what you are doing . MySQL’s full-text search capability has few user-tunable parameters. You can exert more control over full- text searching behavior if you have a MySQL source distribution because some changes require source code modifications. See Section 2.9, “Installing MySQL from Source” . •The ’%’ character is not a supported wildcard character for full-text searches. The remarks for  utf8  also apply to  utf8mb4 , and the remarks for  ucs2  also apply to  utf16 ,  utf16le , and  utf32 . •Full-text searches are supported for  InnoDB  and  MyISAM  tables only. •Full-text searches are not supported for partitioned tables. See Section 24.6, “Restrictions and Limitations on Partitioning” . •Full-text searches can be used with most multibyte character sets. The exception is that for Unicode, the utf8  character set can be used, but not the  ucs2  character set. Although  FULLTEXT  indexes on  ucs2 columns cannot be used, you can perform  IN BOOLEAN MODE  searches on a  ucs2  column that has no such index. •Ideographic languages such as Chinese and Japanese do not have word delimiters. Therefore, the built- in full-text parser  cannot determine where words begin and end in these and other such languages . •Although the use of multiple character sets within a single table is supported, all columns in a  FULLTEXT index must use the same character set and collation. •The  MATCH()  column list must match exactly the column list in some  FULLTEXT  index definition for the table, unless this  MATCH()  is  IN BOOLEAN MODE  on a  MyISAM  table. For  MyISAM  tables, boolean- mode searches can be done on nonindexed columns, although they are likely to be slow. •The argument to  AGAINST()  must be a string value that is constant during query evaluation. This rules out, for example, a table column because that can differ for each row. •Index hints are more limited for  FULLTEXT  searches than for non- FULLTEXT  searches. See Section 8.9.4, “Index Hints” . •For  InnoDB , all DML operations ( INSERT ,  UPDATE ,  DELETE ) involving columns with full-text indexes are processed at transaction commit time. For example, for an  INSERT  operation, an inserted string is tokenized and decomposed into individual words. The individual words are then added to full-text index tables when the transaction is committed. As a result, full-text searches only return committed data. A character-based ngram full-text parser that supports Chinese, Japanese, and Korean (CJK), and a word-based MeCab parser plugin that supports Japanese are provided for use with  InnoDB  and  MyISAM tables. who’s why within wouldn’t you’ll yourself whoever will without yes you’re yourselves whole willing won’t yet you’ve zero whom wish wonder you your whose with would you’d yours