To enable and use MySQL full-text index, 1. Make sure that the table engine is InnoDB or MyISAM, add FULLTEXT index when creating or modifying tables; 2. Use MATCH...AGAINST syntax to perform searches, default natural language mode, and use Boolean mode to improve flexibility; 3. Pay attention to keyword length, common word limitations and matching issues, and adjust ft_min_word_len, use Boolean mode or combine sorting optimization results; 4. In terms of performance, avoid frequent updates of fields to build indexes, control the number of index fields and maintain them regularly; 5. Chinese support is weak, and can be solved through ngram plug-in, application-layer word segmentation or external search engines.
MySQL's full-text search function is very practical when dealing with text search needs, especially in scenarios such as blogs, forums, e-commerce, etc. where content needs to be quickly searched. Although it is not as powerful as a professional search engine, it is perfectly enough for small and medium-sized projects and is relatively simple to implement.

How to enable and use MySQL full-text indexing?
To use full-text search, you must first make sure your table engine is InnoDB
or MyISAM
(InnoDB is recommended), and then add a FULLTEXT
index when creating a table or modifying the table structure.
For example:

CREATE TABLE articles ( id INT UNSIGNED AUTO_INCREMENT NOT NULL PRIMARY KEY, title VARCHAR(200), body TEXT, FULLTEXT (title, body) ) ENGINE=InnoDB;
After inserting the data, you can use MATCH ... AGAINST
syntax to perform full text search:
SELECT * FROM articles WHERE MATCH(title, body) AGAINST('keyword');
The default is natural language mode, and you can also specify other modes, such as Boolean mode:

SELECT * FROM articles WHERE MATCH(title, body) AGAINST('Keyword*' IN BOOLEAN MODE);
Boolean mode supports more flexible query methods, such as wildcards, exclusion words, etc.
FAQs and Optimization Suggestions
The query results are not ideal?
Sometimes you will find that you can't search for what you expect, which may be due to the following reasons:
- The keyword is too short, the default minimum length is 4, which can be adjusted by
ft_min_word_len
; - Search terms appear in more than 50% of records and are considered "common words" and ignored;
- The natural language pattern is used, and the matching degree is not high enough.
suggestion:
- If your business has a lot of short keywords, such as technical terms, abbreviations, etc., it is recommended to change
ft_min_word_len
to 3 or lower; - For low matching problems, you can try Boolean mode to improve accuracy with operators;
- You can sort it in combination with
ORDER BY MATCH... AGAINST()
to make the more relevant rank ahead.
What should I do if I can’t improve my performance?
Although the full text index is fast, it is not omnipotent. If your data volume is large and concurrency is high, you should still pay attention to some details:
- Avoid creating full-text indexes on frequently updated fields;
- Reasonably control the number of index fields and do not add them all;
- Do
ANALYZE TABLE
andOPTIMIZE TABLE
regularly to keep index statistics accurate; - Don't expect it to replace professional search engines like Elasticsearch. It's better to leave complex scenarios to them.
How about Chinese support?
MySQL native full-text search supports Chinese weakly because it relies on the space word segmentation mechanism, while Chinese has no spaces. So if you use it directly, you will find that searching for Chinese is basically invalid.
Solution:
- Use third-party plugins such as
ngram
word segmenter (for MySQL 5.7); - At the application layer, participle words by themselves, save the words in separate fields and then create a full text index;
- Or simply use external search engines, such as Elasticsearch Logstash to import data.
Basically that's it. MySQL's full-text search function can save a lot of trouble if it is used well, but don't expect too much. The key is to choose a reasonable plan based on the actual scenario.
The above is the detailed content of MySQL Full-Text Search Implementation and Tuning. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

TosecurelyconnecttoaremoteMySQLserver,useSSHtunneling,configureMySQLforremoteaccess,setfirewallrules,andconsiderSSLencryption.First,establishanSSHtunnelwithssh-L3307:localhost:3306user@remote-server-Nandconnectviamysql-h127.0.0.1-P3307.Second,editMyS

mysqldump is a common tool for performing logical backups of MySQL databases. It generates SQL files containing CREATE and INSERT statements to rebuild the database. 1. It does not back up the original file, but converts the database structure and content into portable SQL commands; 2. It is suitable for small databases or selective recovery, and is not suitable for fast recovery of TB-level data; 3. Common options include --single-transaction, --databases, --all-databases, --routines, etc.; 4. Use mysql command to import during recovery, and can turn off foreign key checks to improve speed; 5. It is recommended to test backup regularly, use compression, and automatic adjustment.

Turn on MySQL slow query logs and analyze locationable performance issues. 1. Edit the configuration file or dynamically set slow_query_log and long_query_time; 2. The log contains key fields such as Query_time, Lock_time, Rows_examined to assist in judging efficiency bottlenecks; 3. Use mysqldumpslow or pt-query-digest tools to efficiently analyze logs; 4. Optimization suggestions include adding indexes, avoiding SELECT*, splitting complex queries, etc. For example, adding an index to user_id can significantly reduce the number of scanned rows and improve query efficiency.

When handling NULL values ??in MySQL, please note: 1. When designing the table, the key fields are set to NOTNULL, and optional fields are allowed NULL; 2. ISNULL or ISNOTNULL must be used with = or !=; 3. IFNULL or COALESCE functions can be used to replace the display default values; 4. Be cautious when using NULL values ??directly when inserting or updating, and pay attention to the data source and ORM framework processing methods. NULL represents an unknown value and does not equal any value, including itself. Therefore, be careful when querying, counting, and connecting tables to avoid missing data or logical errors. Rational use of functions and constraints can effectively reduce interference caused by NULL.

ForeignkeysinMySQLensuredataintegritybyenforcingrelationshipsbetweentables.Theypreventorphanedrecords,restrictinvaliddataentry,andcancascadechangesautomatically.BothtablesmustusetheInnoDBstorageengine,andforeignkeycolumnsmustmatchthedatatypeoftherefe

To reset the root password of MySQL, please follow the following steps: 1. Stop the MySQL server, use sudosystemctlstopmysql or sudosystemctlstopmysqld; 2. Start MySQL in --skip-grant-tables mode, execute sudomysqld-skip-grant-tables&; 3. Log in to MySQL and execute the corresponding SQL command to modify the password according to the version, such as FLUSHPRIVILEGES;ALTERUSER'root'@'localhost'IDENTIFIEDBY'your_new

To view the size of the MySQL database and table, you can query the information_schema directly or use the command line tool. 1. Check the entire database size: Execute the SQL statement SELECTtable_schemaAS'Database',SUM(data_length index_length)/1024/1024AS'Size(MB)'FROMinformation_schema.tablesGROUPBYtable_schema; you can get the total size of all databases, or add WHERE conditions to limit the specific database; 2. Check the single table size: use SELECTta

Character set and sorting rules issues are common when cross-platform migration or multi-person development, resulting in garbled code or inconsistent query. There are three core solutions: First, check and unify the character set of database, table, and fields to utf8mb4, view through SHOWCREATEDATABASE/TABLE, and modify it with ALTER statement; second, specify the utf8mb4 character set when the client connects, and set it in connection parameters or execute SETNAMES; third, select the sorting rules reasonably, and recommend using utf8mb4_unicode_ci to ensure the accuracy of comparison and sorting, and specify or modify it through ALTER when building the library and table.
