Primary keys uniquely identify rows in a table, while foreign keys establish relationships between tables. A primary key must have unique, non-null values and each table can have only one; it can be a single column or a composite of multiple columns. Foreign keys reference the primary key in another table to ensure referential integrity, preventing orphaned records. They support actions like ON DELETE CASCADE or ON UPDATE CASCADE to automate data consistency. Primary keys are essential for uniqueness and fast access, often using auto-incrementing integers or UUIDs, while foreign keys are used whenever tables are related, such as linking users to orders or blog posts to authors. Common pitfalls include missing indexes on foreign keys, improper handling of dependent records, using strings for IDs, and choosing storage engines that do not support foreign keys.
Primary keys and foreign keys are the backbone of relational databases like MySQL. They help maintain data integrity and establish relationships between tables. If you're just starting with MySQL, understanding how these keys work is crucial for building solid database structures.

What’s a Primary Key?
A primary key is a column (or combination of columns) that uniquely identifies each row in a table. Think of it as an ID card for your records — no two rows can have the same value in the primary key column(s).

Here’s what makes a primary key special:
- It must contain unique values.
- It cannot contain
NULL
values. - Each table can have only one primary key, though it may consist of multiple columns (called a composite key).
For example, in a users
table, you might use user_id
as the primary key:

CREATE TABLE users ( user_id INT PRIMARY KEY, name VARCHAR(100) );
Or if you want to define it separately (especially useful when creating composite keys):
CREATE TABLE orders ( order_id INT, product_code CHAR(10), amount DECIMAL(10,2), PRIMARY KEY (order_id, product_code) );
This ensures that the combination of order_id
and product_code
is unique across the table.
What’s a Foreign Key?
A foreign key is a field (or collection of fields) in one table that refers to the primary key in another table. The main purpose is to ensure referential integrity — meaning you can't have a record pointing to something that doesn’t exist.
Let's say we have a users
table and an orders
table. To link each order to a specific user, we’d add a foreign key:
CREATE TABLE orders ( order_id INT PRIMARY KEY, user_id INT, total DECIMAL(10,2), FOREIGN KEY (user_id) REFERENCES users(user_id) );
Now, if someone tries to insert an order with a user_id
that doesn’t exist in the users
table, MySQL will stop them from doing it.
You can also set what happens when the referenced row changes:
ON DELETE CASCADE
: If the user gets deleted, all their orders get deleted too.ON UPDATE CASCADE
: If theuser_id
changes (unlikely but possible), the change propagates to theorders
table.ON DELETE SET NULL
: If the user is deleted, the foreign key becomesNULL
. Note: the column must allowNULL
values for this to work.
Example:
FOREIGN KEY (user_id) REFERENCES users(user_id) ON DELETE CASCADE ON UPDATE CASCADE
This helps automate cleanup and avoid orphaned records.
When to Use Primary and Foreign Keys
Use a primary key whenever you need to guarantee uniqueness and fast access to rows. Most tables should have one — typically an auto-incrementing integer (AUTO_INCREMENT
) or a UUID.
Use a foreign key whenever there's a clear relationship between tables. For example:
- A blog post belongs to an author.
- An invoice has multiple line items.
- A customer can place many orders.
Some common pitfalls to watch out for:
- Forgetting to create indexes on foreign key columns (MySQL usually does this automatically).
- Trying to delete or update a referenced row without handling dependent records first.
- Using strings instead of numeric IDs for foreign keys — slower and more error-prone.
Also, keep in mind that not all storage engines support foreign keys. InnoDB does; MyISAM does not. So always make sure you're using InnoDB unless you have a good reason not to.
That’s basically how primary and foreign keys work in MySQL. They’re pretty straightforward once you get used to thinking in terms of relationships and constraints.
The above is the detailed content of mysql tutorial about foreign keys and primary keys. 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

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.

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

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

IndexesinMySQLimprovequeryspeedbyenablingfasterdataretrieval.1.Theyreducedatascanned,allowingMySQLtoquicklylocaterelevantrowsinWHEREorORDERBYclauses,especiallyimportantforlargeorfrequentlyqueriedtables.2.Theyspeedupjoinsandsorting,makingJOINoperation

InnoDB is MySQL's default storage engine because it outperforms other engines such as MyISAM in terms of reliability, concurrency performance and crash recovery. 1. It supports transaction processing, follows ACID principles, ensures data integrity, and is suitable for key data scenarios such as financial records or user accounts; 2. It adopts row-level locks instead of table-level locks to improve performance and throughput in high concurrent write environments; 3. It has a crash recovery mechanism and automatic repair function, and supports foreign key constraints to ensure data consistency and reference integrity, and prevent isolated records and data inconsistencies.

MySQL's default transaction isolation level is RepeatableRead, which prevents dirty reads and non-repeatable reads through MVCC and gap locks, and avoids phantom reading in most cases; other major levels include read uncommitted (ReadUncommitted), allowing dirty reads but the fastest performance, 1. Read Committed (ReadCommitted) ensures that the submitted data is read but may encounter non-repeatable reads and phantom readings, 2. RepeatableRead default level ensures that multiple reads within the transaction are consistent, 3. Serialization (Serializable) the highest level, prevents other transactions from modifying data through locks, ensuring data integrity but sacrificing performance;

MySQL transactions follow ACID characteristics to ensure the reliability and consistency of database transactions. First, atomicity ensures that transactions are executed as an indivisible whole, either all succeed or all fail to roll back. For example, withdrawals and deposits must be completed or not occur at the same time in the transfer operation; second, consistency ensures that transactions transition the database from one valid state to another, and maintains the correct data logic through mechanisms such as constraints and triggers; third, isolation controls the visibility of multiple transactions when concurrent execution, prevents dirty reading, non-repeatable reading and fantasy reading. MySQL supports ReadUncommitted and ReadCommi.

To add MySQL's bin directory to the system PATH, it needs to be configured according to the different operating systems. 1. Windows system: Find the bin folder in the MySQL installation directory (the default path is usually C:\ProgramFiles\MySQL\MySQLServerX.X\bin), right-click "This Computer" → "Properties" → "Advanced System Settings" → "Environment Variables", select Path in "System Variables" and edit it, add the MySQLbin path, save it and restart the command prompt and enter mysql--version verification; 2.macOS and Linux systems: Bash users edit ~/.bashrc or ~/.bash_
