Full-text searches are not supported for partitioned tables. See Section 18.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
ucs2 character set. Although
FULLTEXT indexes on
ucs2 columns cannot be used, you can
IN BOOLEAN MODE searches on a
ucs2 column that has no such index.
The remarks for
utf8 also apply to
utf8mb4, and the remarks for
ucs2 also apply to
Ideographic languages such as Chinese and Japanese do not
have word delimiters. Therefore, the
FULLTEXT parser cannot
determine where words begin and end in these and other such
languages. The implications of this and some
workarounds for the problem are described in
Section 12.9, “Full-Text Search Functions”.
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.
MATCH() column list must
match exactly the column list in some
FULLTEXT index definition for the table,
IN BOOLEAN MODE on a
MyISAM table. For
MyISAM tables, boolean-mode searches can
be done on nonindexed columns, although they are likely to
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
searches than for non-
See Section 220.127.116.11, “Index Hint Syntax”.
InnoDB, all DML operations
DELETE) involving columns
with full-text indexes are processed at transaction commit
time. For example, for an
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.