MySQL common index, unique index, primary index, foreign key index, composite index, full-text index usage, mysql full-text index

MySQL common index, unique index, primary index, foreign key index, composite index, full-text index usage, mysql full-text index
1. Common Index
The only task of a common INDEX (INDEX defined by the KEY or INDEX keyword) is to speed up data access. Therefore, you should create an index only for the data columns that most frequently appear in the query condition (WHERE column =...) or sort condition (order by column. If possible, you should select the most neat and compact data column (such as an integer data column) to create an index.
　　2. Unique Index
Normal indexes allow indexed data columns to contain duplicate values. For example, because a person may have the same name, the same name may appear twice or more times in the same "employee profile" data table.
If you can determine that a data column will only contain different values, you should use the keyword UNIQUE to define it as a UNIQUE index when creating an index for this data column. The advantage of doing so: First, it simplifies MySQL's management of this index, and this index becomes more efficient. Second, MySQL inserts a data table with a new record, automatically checks whether the value of this field of the new record has already exists in this field of a record; if yes, MySQL rejects the insert of that new record. That is to say, the unique index can ensure the uniqueness of data records. In fact, in many cases, the purpose of creating a unique index is not to speed up access, but to avoid data duplication.
　　3. Primary Index
I have already repeatedly stressed that an index must be created for the primary key field. This index is called "Primary Index ". The only difference between a PRIMARY index and a UNIQUE index is that the keywords used by the former during definition are PRIMARY rather than UNIQUE.
　　4. Foreign Key Index
If a foreign key constraint is defined for a foreign key field, MySQL defines an internal index to help you manage and use foreign key constraints in the most efficient way.
　　5. Composite Index
Indexes can cover multiple data columns, such as INDEX (columnA, columnB) indexes. This index features that MySQL can selectively use such an index. If you only need to use an INDEX on the columnA data column for the query operation, you can use a composite INDEX (columnA, columnB ). However, this method is only applicable to the combination of data columns in the composite index. For example, INDEX (A, B, C) can be used as an INDEX of A or (A, B), but cannot be used as B, C or (B, C).
　　
　　6. Full-text index
A common index on a text field can only accelerate the retrieval of strings (characters starting with the field content) at the top of the field content. If a field contains a large text segment consisting of several or even multiple words, the normal index will be useless. This kind of search usually appears in the form of LIKE % word %, which is very complicated for MySQL. If the amount of data to be processed is large, the response time will be very long.
This type of scenario is where full-text indexes can be used. When an index of this type is generated, MySQL creates a list of all the words that appear in the text, and searches for relevant data records based on the list. The full-text index can be created along with the data table, or you can use the following command to add a full-text index if necessary in the future:
Alter table tablename add fulltext (column1, column2)
With full-text indexes, you can use the SELECT query command to retrieve data records containing one or more given words. The basic syntax for such query commands is as follows:
SELECT * FROM tablename
Where match (column1, column2) AGAINST ('word1 ', 'word2', 'word3 ')
The preceding command will query all the data records of word1, word2, and word3 in column1 and column2 fields.
　　Annotation: InnoDB data tables do not support full-text indexing.

　　Query and INDEX OPTIMIZATION
The performance test results are of practical reference only when the database has enough test data. If there are only several hundred data records in the test database, they are usually loaded into the memory after the first query command is executed, this will make subsequent query commands run very fast-whether or not indexes are used. The database performance test results are meaningful only when the number of records in the database exceeds 1000 and the total amount of data exceeds the total memory on the MySQL server.
People often get some help from the explain select command when they are not sure which columns should be used to create indexes. In fact, this simply adds an EXPLAIN keyword to a common SELECT command as the prefix. With this keyword, MySQL will not execute the SELECT command, but analyze it. MySQL lists the query execution process and indexes (if any) in the form of tables.
In the output result of the EXPLAIN command, the 1st columns are the names of the data tables read from the database, which are listed in the read order. The type column specifies the JOIN relationship between the data table and other data tables ). Among various types of associations, the most efficient is system, followed by const, eq_ref, ref, range, index, and All (All means: corresponding to each record in the data table at the upper level, all records in the data table must be read once-this situation can be avoided by a single line ).
The possible_keys data column lists the indexes available for MySQL to search for data records. The key data column is the index actually selected by MySQL. The length of this index calculated in bytes is provided in the key_len data column. For example, for an INTEGER data column index, the length of this Byte will be 4. If a composite index is used, you can also see which parts of MySQL are used in the key_len data column. As a general rule, the smaller the value in the key_len data column, the better (faster ).
The ref data column provides the name of the data column in another data table in the association relationship. The row data column is the number of data rows that MySQL expects to read from the data table when executing this query. The product of all numbers in the row data column gives us a general idea of the number of combinations to be processed in this query.