Summary of usage differences of MySQL Count function
Preface
Hello everyone, how much do you know about Count in MySQL?
The demand for statistical data is very easy to encounter in our daily development. Well, MySQL also supports a variety of calculation functions.
Next, let’s take a look at the differences between them and whether they have any pitfalls. [Recommended learning: MySQL video tutorial]
The difference between count(*), count(1), and count(id)
The meaning of count: count() is an aggregate function. The returned result set is judged row by row. If the parameter of the count function is not NULL, the cumulative value will be increased by 1, otherwise it will not be added. Finally, the cumulative value is returned.
count (field) is special, it means returning the total number of data rows that meet the conditions, and the parameter "field" is not NULL
Analysis Performance difference principle
Give the server layer whatever it wants;
InnoDB only gives necessary values;
The current optimizer only optimizes the semantics of count(*) to "get the number of rows", and does not do other "obvious" optimizations
Example:
count (primary key id), the InnoDB engine will traverse the entire table, take out the id value of each row, and return it to the server layer. After the server layer gets the id, it judges that it cannot be empty, so it accumulates it row by row.
count(1), the InnoDB engine traverses the entire table but does not take values. The server layer puts a number "1" into each row returned. If it is judged that it cannot be empty, it is accumulated by row.
count (field), if the server needs a field, it will return the field. If the field is empty, statistics will not be performed. If the value of the field is too large, it will cause low efficiency.
count(字段)<count(主键 id)<count(1)≈count(*)
##Why is count(*) the fastest?
The optimizer does its job and finds the smallest number to traverse. InnoDB is an index-organized table. The leaf nodes of the primary key index tree are data, while the leaf nodes of the ordinary index tree are the primary key values. Therefore, the ordinary index tree is much smaller than the primary key index tree. For operations such as count(*), the results obtained by traversing any index tree are logically the same. Therefore, the MySQL optimizer will find the smallest tree to traverse. On the premise of ensuring that the logic is correct, minimizing the amount of data scanned is one of the general rules of database system design.// 数据中存在null值数据 select count(*) from audit_log a; 结果:1 select count(id) from audit_log a; 结果:0We see that the results of count are inconsistent. The number of records should be 1, but count(id) is not. Equal to 0This is because count (field) is not counted and the field value is nullSo when the field is a non-empty field, you need to use count(*) to solve it this problem.
- MyISAM table although count(*) is fast, it does not support transactions;
- Although the show table status command returns quickly, it is not accurate;
- InnoDB table direct count(*) will traverse the entire table, although The results are accurate, but can cause performance issues.
The above is the detailed content of Summary of usage differences of MySQL Count function. 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)

To add a primary key to an existing table, use the ALTERTABLE statement with the ADDPRIMARYKEY clause. 1. Ensure that the target column has no NULL value, no duplication and is defined as NOTNULL; 2. The single-column primary key syntax is ALTERTABLE table name ADDPRIMARYKEY (column name); 3. The multi-column combination primary key syntax is ALTERTABLE table name ADDPRIMARYKEY (column 1, column 2); 4. If the column allows NULL, you must first execute MODIFY to set NOTNULL; 5. Each table can only have one primary key, and the old primary key must be deleted before adding; 6. If you need to increase it yourself, you can use MODIFY to set AUTO_INCREMENT. Ensure data before operation

B-TreeindexesarebestformostPHPapplications,astheysupportequalityandrangequeries,sorting,andareidealforcolumnsusedinWHERE,JOIN,orORDERBYclauses;2.Full-Textindexesshouldbeusedfornaturallanguageorbooleansearchesontextfieldslikearticlesorproductdescripti

Using mysqldump is the most common and effective way to back up MySQL databases. It can generate SQL scripts containing table structure and data. 1. The basic syntax is: mysqldump-u[user name]-p[database name]>backup_file.sql. After execution, enter the password to generate a backup file. 2. Back up multiple databases with --databases option: mysqldump-uroot-p--databasesdb1db2>multiple_dbs_backup.sql. 3. Back up all databases with --all-databases: mysqldump-uroot-p

You can customize the separator by using the SEPARATOR keyword in the GROUP_CONCAT() function; 1. Use SEPARATOR to specify a custom separator, such as SEPARATOR'; 'The separator can be changed to a semicolon and plus space; 2. Common examples include using the pipe character '|', space'', line break character '\n' or custom string '->' as the separator; 3. Note that the separator must be a string literal or expression, and the result length is limited by the group_concat_max_len variable, which can be adjusted by SETSESSIONgroup_concat_max_len=10000; 4. SEPARATOR is optional

UNIONremovesduplicateswhileUNIONALLkeepsallrowsincludingduplicates;1.UNIONperformsdeduplicationbysortingandcomparingrows,returningonlyuniqueresults,whichmakesitsloweronlargedatasets;2.UNIONALLincludeseveryrowfromeachquerywithoutcheckingforduplicates,

The table can be locked manually using LOCKTABLES. The READ lock allows multiple sessions to read but cannot be written. The WRITE lock provides exclusive read and write permissions for the current session and other sessions cannot read and write. 2. The lock is only for the current connection. Execution of STARTTRANSACTION and other commands will implicitly release the lock. After locking, it can only access the locked table; 3. Only use it in specific scenarios such as MyISAM table maintenance and data backup. InnoDB should give priority to using transaction and row-level locks such as SELECT...FORUPDATE to avoid performance problems; 4. After the operation is completed, UNLOCKTABLES must be explicitly released, otherwise resource blockage may occur.

To select data from MySQL table, you should use SELECT statement, 1. Use SELECTcolumn1, column2FROMtable_name to obtain the specified column, or use SELECT* to obtain all columns; 2. Use WHERE clause to filter rows, such as SELECTname, ageFROMusersWHEREage>25; 3. Use ORDERBY to sort the results, such as ORDERBYageDESC, representing descending order of age; 4. Use LIMIT to limit the number of rows, such as LIMIT5 to return the first 5 rows, or use LIMIT10OFFSET20 to implement paging; 5. Use AND, OR and parentheses to combine

TheINoperatorinMySQLchecksifavaluematchesanyinaspecifiedlist,simplifyingmultipleORconditions;itworkswithliterals,strings,dates,andsubqueries,improvesqueryreadability,performswellonindexedcolumns,supportsNOTIN(withcautionforNULLs),andcanbecombinedwith
