The core method for getting the last inserted ID in MySQL is to use the LAST_INSERT_ID() function, which returns the autoincrement ID generated by the last insertion in the current connection. 1. Get the ID directly after insertion: Call LAST_INSERT_ID() immediately after executing the INSERT statement, which is suitable for tables with self-increment primary keys; 2. Use in programming languages: For example, PDO extension of PHP calls the function through lastInsertId() and Python's mysql-connector encapsulated; 3. Performance when inserting multiple lines: Return the ID of the first insert record, not the last; 4. Notes include: connection isolation ensures that it is not affected by other connections, it is also applicable in transactions, does not support non-self-increment fields, and pay attention to the call order in stored procedures. Mastering these key points can safely and effectively obtain the last inserted ID.
The most common method to get the last inserted ID in MySQL is to use LAST_INSERT_ID()
function. This function returns the autoincrement ID generated by the last INSERT
operation in the current connection, and it is at the connection level and will not be affected by other connection operations.

Below are some specific scenarios and usage methods that you may use.
Basic usage: Get the ID directly after inserting
This is the most common usage. After you have executed an INSERT
statement, immediately call LAST_INSERT_ID()
to get the autoincrement primary key value of the record just inserted.

INSERT INTO users (name, email) VALUES ('Tom', 'tom@example.com'); SELECT LAST_INSERT_ID();
- This method is only applicable to tables with autoincrement primary keys (
AUTO_INCREMENT
). - Regardless of whether you explicitly pass in the primary key value, as long as this insert triggers the generation of the self-increment field,
LAST_INSERT_ID()
can get the correct value.
Used in programming languages: Take PHP and Python as examples
Most database drivers or ORMs encapsulate calls to LAST_INSERT_ID()
, but understanding the underlying mechanism is still important.
PHP (PDO)
$pdo->exec("INSERT INTO users (name, email) VALUES ('Jerry', 'jerry@example.com')"); $lastId = $pdo->lastInsertId();
Python (using mysql-connector)
cursor.execute("INSERT INTO users (name, email) VALUES (%s, %s)", ("Lucy", "lucy@example.com")) print(cursor.lastrowid)
Behind these encapsulations are actually calling MySQL's LAST_INSERT_ID()
function.

Performance when inserting multiple lines
If you insert multiple pieces of data at once, LAST_INSERT_ID()
returns the ID of the first inserted record.
INSERT INTO users (name, email) VALUES ('A', 'a@example.com'), ('B', 'b@example.com'), ('C', 'c@example.com'); SELECT LAST_INSERT_ID(); -- Returns the ID of the first record
For example, if the start ID is 100, then the three records are 100, 101, and 102, respectively, and LAST_INSERT_ID()
returns 100.
This needs to be paid attention to in some batch import logic.
Notes and FAQs
- Connection isolation : Each connection has its own independent
LAST_INSERT_ID()
, so you don't have to worry about being affected by insertion by other users. - It is also applicable in transactions : you can get the ID normally even if you perform insertions in a transaction.
- Non-self-increment fields are not supported : if the generated ID is not inserted through the self-increment field, such as a UUID or manually specifying the primary key, then this function will not be used.
- Don't use it randomly in stored procedures : Pay attention to the order when calling it in stored procedures, otherwise you may not get the correct value.
Basically that's it. By mastering the usage scenarios and limitations of LAST_INSERT_ID()
, you can safely obtain the ID of the newly inserted record during development.
The above is the detailed content of how to get last inserted id 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

The key to installing MySQL 8.0 is to follow the steps and pay attention to common problems. It is recommended to use the MSI installation package on Windows. The steps include downloading the installation package, running the installer, selecting the installation type, setting the root password, enabling service startup, and paying attention to port conflicts or manually configuring the ZIP version; Linux (such as Ubuntu) is installed through apt, and the steps are to update the source, installing the server, running security scripts, checking service status, and modifying the root authentication method; no matter which platform, you should modify the default password, create ordinary users, set up firewalls, adjust configuration files to optimize character sets and other parameters to ensure security and normal use.

Enable MySQL's SSL/TLS encryption connection can effectively prevent data leakage. The specific steps are as follows: 1. Confirm that the MySQL version supports SSL, and check whether the return value is YES through SHOWVARIABLESLIKE'have_ssl'; 2. Prepare a PEM format certificate file (ca.pem, server-cert.pem, server-key.pem), which can be generated through OpenSSL or obtained from CA; 3. Modify the MySQL configuration file, add ssl-ca, ssl-cert and ssl-key paths in the [mysqld] section and restart the service; 4. Force the client to use SSL, and use CREATEUSER

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.

MySQL's binary log (binlog) is a binary log that records database change operations, and is used in scenarios such as data recovery, master-slave replication and auditing. 1. Binlog is a logical log file that records all operation events that modify data, such as INSERT, UPDATE, DELETE, etc., but does not include SELECT or SHOW query statements; 2. Its main uses include: data recovery through replay logs, supporting master-slave copying to achieve data synchronization, and used to analyze operation records to meet audit requirements; 3. Enable binlog requires setting log-bin, server-id, binlog_format and expire_logs_day in the configuration file.

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.

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

Toalteralargeproductiontablewithoutlonglocks,useonlineDDLtechniques.1)IdentifyifyourALTERoperationisfast(e.g.,adding/droppingcolumns,modifyingNULL/NOTNULL)orslow(e.g.,changingdatatypes,reorderingcolumns,addingindexesonlargedata).2)Usedatabase-specifi
