Upsert in SQL

Upsert in SQL

Anton Zhiyanov is currently on a one-man quest to write detailed documentation for all of the fundamental SQL operations, comparing and contrasting how they work across multiple engines, generally with interactive examples.

Useful tips in here on why "insert... on conflict" is usually a better option than "insert or replace into" because the latter can perform a delete and then an insert, firing triggers that you may not have wanted to be fired.

Via Hacker News

conflict databases documentation examples interactive multiple operations postgresql sql sqlite tips work