content_image/774164.jpg
+-----------+ 15 rows in set (0.00 sec) 

To create stopword lists on a table-by-table basis, create other stopword tables and use the innodb_ft_user_stopword_table  option to specify the stopword table that you want to use before you create the full-text index. 

## Stopwords for MyISAM Search Indexes 

The stopword file is loaded and searched using latin1  if character_set_server  is ucs2 , utf16 , utf16le , or utf32 . 

To override the default stopword list for MyISAM tables, set the ft_stopword_file  system variable. (See Section 5.1.8, “Server System Variables” .) The variable value should be the path name of the file containing the stopword list, or the empty string to disable stopword filtering. The server looks for the file in the data directory unless an absolute path name is given to specify a different directory. After changing the value of this variable or the contents of the stopword file, restart the server and rebuild your FULLTEXT indexes. 

The stopword list is free-form, separating stopwords with any nonalphanumeric character such as newline, space, or comma. Exceptions are the underscore character ( _ ) and a single apostrophe ( ’ ) which are treated as part of a word. The character set of the stopword list is the server’s default character set; see Section 10.3.2, “Server Character Set and Collation” . 

The following list shows the default stopwords for MyISAM  search indexes. In a MySQL source distribution, you can find this list in the storage/myisam/ft_static.c  file. 

<img src='content_image/774164.jpg'>

