COMMIT
The SQL statement that ends a transaction and makes all its changes permanent and visible to others.
In more detail
Commit is the point readers rely on. Before it, other sessions do not see the changes; after it, the changes survive a crash or power loss.
Example
In this course: code that commits its own transactions cannot be isolated by a rolled-back test transaction; give it a fresh schema or database instead.Related terms
- transaction — A group of database changes that succeed or fail together, so the data is never left half-updated.
- BEGIN — The SQL statement that starts a transaction, so the following statements form one unit.
- ROLLBACK — The SQL statement that ends a transaction by undoing every change made since it began.
- ACID — The four guarantees of a database transaction: atomicity, consistency, isolation and durability.
Taught in
- Security Baselines, Policies & Hardening Standards — Cybersecurity Fundamentals, GRC & Cryptography
- Cryptographic Hashing: SHA-256, SHA-3 & Passwords — Cybersecurity Fundamentals, GRC & Cryptography
- Privacy Principles, GDPR Subject Rights & Minimization — Cybersecurity Fundamentals, GRC & Cryptography
- Asset Lifecycle Management & Media Sanitization — Cybersecurity Fundamentals, GRC & Cryptography
- Disaster Recovery Sites: Hot, Warm & Cold — Cybersecurity Fundamentals, GRC & Cryptography
- Transactions And ACID Properties — PostgreSQL, Indexing & Relational Data Modeling
- Isolation Levels And The Lost Update — PostgreSQL, Indexing & Relational Data Modeling
- Testing With Real Databases — Automated Testing, TDD & Quality Engineering