The key to creating a MySQL table is to master the basic syntax and common options of CREATE TABLE statements. 1. The basic syntax requires specifying field names, data types and constraints, such as NOT NULL, PRIMARY KEY, AUTO_INCREMENT; 2. Common field types include INT, VARCHAR(n), TEXT, DATE, DATETIME, TIMESTAMP and DECIMAL(m,d), and should be selected according to actual needs to optimize storage and performance; 3. The constraints include NOT NULL, UNIQUE, DEFAULT, PRIMARY KEY and FOREIGN KEY. When using foreign keys, the two tables must be engines that support foreign keys (such as InnoDB); 4. CREATE INDEX can be used. Adding indexes improves query efficiency, but avoids excessive use to avoid affecting write performance; 5. Common errors include field name spelling errors, primary key omissions, data type mismatch, engine not specified, and character set inconsistent. It is recommended to use utf8mb4 uniformly and explicitly declare ENGINE=InnoDB and DEFAULT CHARSET=utf8mb4 in the table creation statement.
When creating a MySQL table, the CREATE TABLE statement is one of the most basic and critical operations. Mastering basic syntax structures and common options can help you design your database more efficiently.
Basic syntax structure
The standard syntax for creating tables in MySQL is as follows:
CREATE TABLE table_name (
column1 datatype constraints,
column2 datatype constraints,
...
); Each field (column) must specify the data type, and constraints can also be added, such as NOT NULL , PRIMARY KEY , AUTO_INCREMENT , etc.
For example, create a user table:
CREATE TABLE users (
id INT NOT NULL AUTO_INCREMENT,
name VARCHAR(50),
email VARCHAR(100) NOT NULL,
created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
PRIMARY KEY (id)
);The above statement contains common uses such as primary key settings, self-increasing fields, and default values.
Common field types and selection suggestions
MySQL supports a variety of field types, commonly used ones include:
-
INT: integer type, suitable for ID, quantity, etc. -
VARCHAR(n): variable length string, suitable for username, title, etc. -
TEXT/LONGTEXT: Large text content, such as the main text of the article -
DATE/DATETIME/TIMESTAMP: Time-dependent, pay attention to time zone processing differences -
DECIMAL(m,d): exact value, suitable for amount field
Some points to pay attention to when selecting a field type:
- Try to choose the appropriate data type according to actual needs to avoid wasting space or restricting expansion
- Don't set the string length to 255 at will, it is more reasonable to set it as needed.
- For fields that are frequently queried, you must first choose the type before considering index optimization.
Key points for constraints and index settings
In addition to field types, common constraints include:
-
NOT NULL: Not allowed to be empty -
UNIQUE: Unique constraints -
DEFAULT value: Set the default value -
PRIMARY KEY: Primary key, generally used with self-increase -
FOREIGN KEY: Foreign key, used to associate other tables
For example, set foreign keys:
CREATE TABLE orders (
order_id INT PRIMARY KEY AUTO_INCREMENT,
user_id INT,
amount DECIMAL(10,2),
FOREIGN KEY (user_id) REFERENCES users(id)
);It should be noted that foreign keys require both tables to use engines that support foreign keys (such as InnoDB).
In addition, if a certain field is often used as query conditions, you can consider adding an index to improve query efficiency:
CREATE INDEX idx_email ON users(email);
But do not over-index, as it will affect the write performance.
Common Errors and Precautions
Probably encountered problems when writing CREATE TABLE statements include:
- The field name is incorrectly spelled or used reserved words. It is recommended that the field name be enclosed in backticks, such as
`order` - Forgot to add
PRIMARY KEYto the primary key, causing the table to not be used normally - Data type mismatch, such as placing long text in
VARCHAR(50) - The engine is not specified, the default may be MyISAM, and you want to use InnoDB
- There is no unified character set, Chinese garbled code, it is recommended to use
utf8mb4uniformly
You can add these settings at the end of the table creation statement:
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;
This can avoid many follow-up problems.
Basically that's it. The grammar is not complicated, but some details are easy to ignore, especially when you are just starting out. Write a few more times and check the document a few times, and you will soon be able to master it.
The above is the detailed content of mysql create table syntax. 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
What is the default username and password for MySQL?
Jun 13, 2025 am 12:34 AM
The default user name of MySQL is usually 'root', but the password varies according to the installation environment; in some Linux distributions, the root account may be authenticated by auth_socket plug-in and cannot log in with the password; when installing tools such as XAMPP or WAMP under Windows, root users usually have no password or use common passwords such as root, mysql, etc.; if you forget the password, you can reset it by stopping the MySQL service, starting in --skip-grant-tables mode, updating the mysql.user table to set a new password and restarting the service; note that the MySQL8.0 version requires additional authentication plug-ins.
What is GTID (Global Transaction Identifier) and what are its advantages?
Jun 19, 2025 am 01:03 AM
GTID (Global Transaction Identifier) ??solves the complexity of replication and failover in MySQL databases by assigning a unique identity to each transaction. 1. It simplifies replication management, automatically handles log files and locations, allowing slave servers to request transactions based on the last executed GTID. 2. Ensure consistency across servers, ensure that each transaction is applied only once on each server, and avoid data inconsistency. 3. Improve troubleshooting efficiency. GTID includes server UUID and serial number, which is convenient for tracking transaction flow and accurately locate problems. These three core advantages make MySQL replication more robust and easy to manage, significantly improving system reliability and data integrity.
How to change or reset the MySQL root user password?
Jun 13, 2025 am 12:33 AM
There are three ways to modify or reset MySQLroot user password: 1. Use the ALTERUSER command to modify existing passwords, and execute the corresponding statement after logging in; 2. If you forget your password, you need to stop the service and start it in --skip-grant-tables mode before modifying; 3. The mysqladmin command can be used to modify it directly by modifying it. Each method is suitable for different scenarios and the operation sequence must not be messed up. After the modification is completed, verification must be made and permission protection must be paid attention to.
What is a typical process for MySQL master failover?
Jun 19, 2025 am 01:06 AM
MySQL main library failover mainly includes four steps. 1. Fault detection: Regularly check the main library process, connection status and simple query to determine whether it is downtime, set up a retry mechanism to avoid misjudgment, and can use tools such as MHA, Orchestrator or Keepalived to assist in detection; 2. Select the new main library: select the most suitable slave library to replace it according to the data synchronization progress (Seconds_Behind_Master), binlog data integrity, network delay and load conditions, and perform data compensation or manual intervention if necessary; 3. Switch topology: Point other slave libraries to the new master library, execute RESETMASTER or enable GTID, update the VIP, DNS or proxy configuration to
How to connect to a MySQL database using the command line?
Jun 19, 2025 am 01:05 AM
The steps to connect to the MySQL database are as follows: 1. Use the basic command format mysql-u username-p-h host address to connect, enter the username and password to log in; 2. If you need to directly enter the specified database, you can add the database name after the command, such as mysql-uroot-pmyproject; 3. If the port is not the default 3306, you need to add the -P parameter to specify the port number, such as mysql-uroot-p-h192.168.1.100-P3307; In addition, if you encounter a password error, you can re-enter it. If the connection fails, check the network, firewall or permission settings. If the client is missing, you can install mysql-client on Linux through the package manager. Master these commands
How does InnoDB implement Repeatable Read isolation level?
Jun 14, 2025 am 12:33 AM
InnoDB implements repeatable reads through MVCC and gap lock. MVCC realizes consistent reading through snapshots, and the transaction query results remain unchanged after multiple transactions; gap lock prevents other transactions from inserting data and avoids phantom reading. For example, transaction A first query gets a value of 100, transaction B is modified to 200 and submitted, A is still 100 in query again; and when performing scope query, gap lock prevents other transactions from inserting records. In addition, non-unique index scans may add gap locks by default, and primary key or unique index equivalent queries may not be added, and gap locks can be cancelled by reducing isolation levels or explicit lock control.
How to alter a large table without locking it (Online DDL)?
Jun 14, 2025 am 12:36 AM
Toalteralargeproductiontablewithoutlonglocks,useonlineDDLtechniques.1)IdentifyifyourALTERoperationisfast(e.g.,adding/droppingcolumns,modifyingNULL/NOTNULL)orslow(e.g.,changingdatatypes,reorderingcolumns,addingindexesonlargedata).2)Usedatabase-specifi
What is the purpose of the InnoDB Buffer Pool?
Jun 12, 2025 am 10:28 AM
The function of InnoDBBufferPool is to improve MySQL read and write performance. It reduces disk I/O operations by cacheing frequently accessed data and indexes into memory, thereby speeding up query speed and optimizing write operations; 1. The larger the BufferPool, the more data is cached, and the higher the hit rate, which directly affects database performance; 2. It not only caches data pages, but also caches index structures such as B-tree nodes to speed up searches; 3. Supports cache "dirty pages", delays writing to disk, reduces I/O and improves write performance; 4. It is recommended to set it to 50%~80% of physical memory during configuration to avoid triggering swap; 5. It can be dynamically resized through innodb_buffer_pool_size, without restarting the instance.
