What is this short article about?
I saw someone ask about the issue of nullable and index in PHPHub migration database file before. I believe that many people who have used MySQL for a long time (especially People who usually pay too much attention to business development) are not very clear about the concepts of these two field attributes. They usually have the following questions:
My field type is not null, why can I insert null values;
Not null is more efficient than null;
When judging that a field is not empty, should we use column '' or should we use column is not null.
With the above questions, let’s take a closer look at the difference between null and not null.
Is null the same as a null value?
First of all, we need to understand the concepts of null value and null:
Null value does not take up space ;
null in MySQL actually takes up space. The following is the official explanation from MYSQL:
NULL columns require additional space in the row to record whether their values ??are NULL . For MyISAM tables, each NULL column takes one bit extra, rounded up to the nearest byte.
For example, you have a cup. The null value means that the cup is vacuum, and the NULL value means that the cup is vacuum. The cup is filled with air. Although the cup looks empty, the difference is huge.
A little chestnut
After understanding the concepts of "null value" and "NULL", the problem is basically clear. Let's test it with an example:
CREATE TABLE `test` (
`col1` VARCHAR( 10 ) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL ,
`col2` VARCHAR( 10 ) CHARACTER SET utf8 COLLATE utf8_general_ci NULL
) ENGINE = MYISAM ;Question 1: My field type is not null, why can I insert null values?
Execute the following SQL, and an error occurs, indicating that Column 'col1' cannot be null.
INSERT INTO `test` VALUES ( null, 1);
One more message, executed successfully.
INSERT INTO `test` VALUES ('',1);
It can be seen that NULL cannot be inserted into NOT NULL fields (isn’t this nonsense?), only null values ??can be inserted, and the answer to question 1 above is there.
Question 2: Why is not null more efficient than null?
Regarding question 2, as we have said above, NULL is not actually a null value, but takes up space. Therefore, when mysql performs comparison, NULL will participate in field comparison, so it will partially affect the efficiency. .
And B-tree indexes will not store NULL values, so if the indexed fields can be NULL, the index efficiency will drop a lot.
Question 3: When judging that a field is not empty, should we use column<>'' or should we use column is not null.
Let's insert a few pieces of data into the test table:
INSERT INTO `test` VALUES ('', NULL); INSERT INTO `test` VALUES ('1', '2');
Now according to the requirements, I want to count all the data in the test table where col1 is not empty. I should use <> ;'' or IS NOT NULL, let's take a look at the difference in results.
The data in the table is now as follows:
Compare the execution effect of the following two SQL sentences respectively
SELECT * FROM `test` WHERE col1 IS NOT NULL
SELECT * FROM `test` WHERE col1 <> ''
As you can see, the results are very different, so we must figure out what kind of search conditions to use and whether to use null based on business needs.
A small pitfall I encountered
When I first joined the company a long time ago and made the first requirement online, I only noticed that the efficiency ratio was not null. null is efficient.
Okay~ When I added fields to the existing table, I set them all to not null, and I felt stupid.
Because many Services have insert actions to operate this table, the result is as you can imagine. Just after it went online, the error Column 'col1' cannot be null filled the mailboxes of everyone in the entire development team.
So, when the business volume is not very large, the use of many technologies actually needs to be comprehensively considered based on the actual situation.
The above is the detailed content of Detailed explanation of NULL and NOT NULL in MySQL. 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
Performing logical backups using mysqldump in MySQL
Jul 06, 2025 am 02:55 AM
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.
Handling NULL Values in MySQL Columns and Queries
Jul 05, 2025 am 02:46 AM
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.
Aggregating data with GROUP BY and HAVING clauses in MySQL
Jul 05, 2025 am 02:42 AM
GROUPBY is used to group data by field and perform aggregation operations, and HAVING is used to filter the results after grouping. For example, using GROUPBYcustomer_id can calculate the total consumption amount of each customer; using HAVING can filter out customers with a total consumption of more than 1,000. The non-aggregated fields after SELECT must appear in GROUPBY, and HAVING can be conditionally filtered using an alias or original expressions. Common techniques include counting the number of each group, grouping multiple fields, and filtering with multiple conditions.
Paginating Results with LIMIT and OFFSET in MySQL
Jul 05, 2025 am 02:41 AM
MySQL paging is commonly implemented using LIMIT and OFFSET, but its performance is poor under large data volume. 1. LIMIT controls the number of each page, OFFSET controls the starting position, and the syntax is LIMITNOFFSETM; 2. Performance problems are caused by excessive records and discarding OFFSET scans, resulting in low efficiency; 3. Optimization suggestions include using cursor paging, index acceleration, and lazy loading; 4. Cursor paging locates the starting point of the next page through the unique value of the last record of the previous page, avoiding OFFSET, which is suitable for "next page" operation, and is not suitable for random jumps.
Calculating Database and Table Sizes in MySQL
Jul 06, 2025 am 02:41 AM
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
Setting up asynchronous primary-replica replication in MySQL
Jul 06, 2025 am 02:52 AM
To set up asynchronous master-slave replication for MySQL, follow these steps: 1. Prepare the master server, enable binary logs and set a unique server-id, create a replication user and record the current log location; 2. Use mysqldump to back up the master library data and import it to the slave server; 3. Configure the server-id and relay-log of the slave server, use the CHANGEMASTER command to connect to the master library and start the replication thread; 4. Check for common problems, such as network, permissions, data consistency and self-increase conflicts, and monitor replication delays. Follow the steps above to ensure that the configuration is completed correctly.
Implementing Transactions and Understanding ACID Properties in MySQL
Jul 08, 2025 am 02:50 AM
MySQL supports transaction processing, and uses the InnoDB storage engine to ensure data consistency and integrity. 1. Transactions are a set of SQL operations, either all succeed or all fail to roll back; 2. ACID attributes include atomicity, consistency, isolation and persistence; 3. The statements that manually control transactions are STARTTRANSACTION, COMMIT and ROLLBACK; 4. The four isolation levels include read not committed, read submitted, repeatable read and serialization; 5. Use transactions correctly to avoid long-term operation, turn off automatic commits, and reasonably handle locks and exceptions. Through these mechanisms, MySQL can achieve high reliability and concurrent control.
Handling character sets and collations issues in MySQL
Jul 08, 2025 am 02:51 AM
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.
