INSERT...ONDUPLICATEKEYUPDATE
Jun 07, 2016 pm 03:55 PM向數(shù)據(jù)庫(kù)插入記錄時(shí),有時(shí)會(huì)有這種需求,當(dāng)符合某種條件的數(shù)據(jù)存在時(shí),去修改它,不存在時(shí),則新增,也就是saveOrUpdate操作。這種控制可以放在業(yè)務(wù)層,也可以放在數(shù)據(jù)庫(kù)層,大多數(shù)數(shù)據(jù)庫(kù)都支持這種需求,如Oracle的merge語(yǔ)句,再如本文所講的MySQL中的INSER
向數(shù)據(jù)庫(kù)插入記錄時(shí),有時(shí)會(huì)有這種需求,當(dāng)符合某種條件的數(shù)據(jù)存在時(shí),去修改它,不存在時(shí),則新增,也就是saveOrUpdate操作。這種控制可以放在業(yè)務(wù)層,也可以放在數(shù)據(jù)庫(kù)層,大多數(shù)數(shù)據(jù)庫(kù)都支持這種需求,如Oracle的merge語(yǔ)句,再如本文所講的MySQL中的INSERT ... ON DUPLICATE KEY UPDATE語(yǔ)句。
該語(yǔ)句是基于唯一索引或主鍵使用,比如一個(gè)字段a被加上了unique index,并且表中已經(jīng)存在了一條記錄值為1,下面兩個(gè)語(yǔ)句會(huì)有相同的效果:
INSERT INTO table (a,b,c) VALUES (1,2,3) ON DUPLICATE KEY UPDATE c=c+1; UPDATE table SET c=c+1 WHERE a=1;ON DUPLICATE KEY UPDATE后面可以放多個(gè)字段,用英文逗號(hào)分割。使用ON DUPLICATE KEY UPDATE,最終如果插入了一個(gè)新行,則受影響的行數(shù)是1,如果修改了已存在的一行數(shù)據(jù),則受影響的行數(shù)是2。
如果字段b也被加上了unique index,則該語(yǔ)句和下面的update語(yǔ)句是等效的:
UPDATE table SET c=c+1 WHERE a=1 OR b=2 LIMIT 1;如果a=1 OR b=2匹配了多行,則只有一行會(huì)被修改。通常的,在ON DUPLICATE KEY UPDATE語(yǔ)句中,我們應(yīng)該避免多個(gè)唯一索引的情況。如果需要插入或更新多條數(shù)據(jù),并且更新的字段需要根據(jù)其它字段來(lái)運(yùn)算時(shí),可以使用如下語(yǔ)句:
INSERT INTO table (a,b,c) VALUES (1,2,3),(4,5,6) ON DUPLICATE KEY UPDATE c=VALUES(a)+VALUES(b);在ON DUPLICATE KEY UPDATE后面使用VALUES()方法,這個(gè)語(yǔ)句等同于下面的兩個(gè)語(yǔ)句:
INSERT INTO table (a,b,c) VALUES (1,2,3) ON DUPLICATE KEY UPDATE c=3;--1+2 INSERT INTO table (a,b,c) VALUES (4,5,6) ON DUPLICATE KEY UPDATE c=9;--4+5如果一個(gè)表中包含了一個(gè)auto_increment的字段,每次insert數(shù)據(jù)后,可以通過(guò)last_insert_id()方法返回最后自動(dòng)生成的值,如果通過(guò)INSERT ... ON DUPLICATE KEY UPDATE語(yǔ)句修改了一條數(shù)據(jù),那么再通過(guò)last_insert_id()方法獲取的值將不正確,實(shí)際測(cè)試中是多了一個(gè)數(shù),比如向表中增加了3條數(shù)據(jù),那么通過(guò)last_insert_id()方法得到的值是3,但是通過(guò)該語(yǔ)句修改了一條數(shù)據(jù)后,通過(guò)last_insert_id()方法得到的值是4。如果想解決該問題,可以通過(guò)如下語(yǔ)句:
INSERT INTO table (a,b,c) VALUES (1,2,3) ON DUPLICATE KEY UPDATE id=LAST_INSERT_ID(id), c=3;
重點(diǎn)是這句id=LAST_INSERT_ID(id)。

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_
