A closer look at explicitly deferred NO ACTION checks and clearing only the optional component of a composite foreign key. These details complement the basic choice between RESTRICT, CASCADE and SET NULL.
postgresql / foreign-key / on-delete / data-retention / cascade / restrict / set-null / referential-integrity
Use ON CONFLICT to atomically insert or update rows based on unique constraints. Specify the exact conflict target, handle duplicate input rows, and understand that excluded values replace, not accumulate.
postgresql / sql / upsert / insert / on-conflict / unique-constraint / concurrency / database
Transactions in PostgreSQL allow grouping SQL operations into atomic blocks using the commands BEGIN, COMMIT, and ROLLBACK. This ensures data integrity: either all changes are applied or none at all. The mechanism is based on ACID principles - atomicity, consistency, isolation, and durability.
PostgreSQL / transactions / BEGIN / COMMIT / ROLLBACK / ACID / savepoint