冪等性的一個要求是屢次操做的結果一致。對於update操做,屢次直接的結果都是最後update的值,是知足需求的。但對於insert,若是已經插入,第二次會報錯,duplicate error, 主鍵重複或者unique key duplicate。因此須要作一下處理。html
最簡單的就是,try-catch,當報錯的時候,調用update去更新,或者策略更簡單點,直接返回就行,不須要更新,以第一條爲準。sql
PostgreSQL從9.5以後就提供了原子的upsert語法: 不存在則插入,發生衝突能夠update。express
官方文檔: https://www.postgresql.org/docs/devel/sql-insert.htmlapp
[ WITH [ RECURSIVE ] with_query [, ...] ] INSERT INTO table_name [ AS alias ] [ ( column_name [, ...] ) ] [ OVERRIDING { SYSTEM | USER} VALUE ] { DEFAULT VALUES | VALUES ( { expression | DEFAULT } [, ...] ) [, ...] | query } [ ON CONFLICT [ conflict_target ] conflict_action ] [ RETURNING * | output_expression [ [ AS ] output_name ] [, ...] ] where conflict_target can be one of: ( { index_column_name | ( index_expression ) } [ COLLATE collation ] [ opclass ] [, ...] ) [ WHERE index_predicate ] ON CONSTRAINT constraint_name and conflict_action is one of: DO NOTHING DO UPDATE SET { column_name = { expression | DEFAULT } | ( column_name [, ...] ) = [ ROW ] ( { expression | DEFAULT } [, ...] ) | ( column_name [, ...] ) = ( sub-SELECT ) } [, ...] [ WHERE condition ]
index_column_namepost
The name of a table_name column. Used to infer arbiter indexes. Follows CREATE INDEX format. SELECT privilege on index_column_name is required.ui
index_expressionspa
Similar to index_column_name, but used to infer expressions on table_name columns appearing within index definitions (not simple columns). Follows CREATE INDEX format. SELECT privilege on any column appearing within index_expression is required.postgresql
建立表code
CREATE TABLE "test"."upsert_test" ( "id" int4 NOT NULL, "name" varchar(255) COLLATE "pg_catalog"."default" ) ;
當主鍵id衝突時,更新其餘字段orm
INSERT INTO test.upsert_test(id, "name") VALUES(1, 'm'),(2, 'n'),(4, 'c') ON conflict(id) DO UPDATE SET "name" = excluded.name;
當主鍵或者unique key發生衝突時,什麼都不作
INSERT INTO test.upsert_test(id, "name") VALUES(1, 'm'),(2, 'n'),(4, 'c') ON conflict(id) DO NOTHING;
原文出處:https://www.cnblogs.com/woshimrf/p/postgresql-upsert.html