Ac Transaction Isolation

Understanding what a database transaction actually guarantees: the isolation levels from read uncommitted to serializable and the anomalies each permits, MVCC and snapshot reads, lost updates and both optimistic and pessimistic resolution, explicit locking and lock ordering deadlocks inside the engine, savepoints and nested work, long transactions and their costs, and the written isolation record. It explains what isolation a query runs under; it never recommends a database product and never promises a result free of anomalies without the level to match. Use when asking "isolation level", "read committed", "repeatable read", "serializable", "MVCC", "snapshot isolation", "lost update", "optimistic locking", "SELECT FOR UPDATE", "deadlock retry", "long transaction", "write skew". Not for schema shape and migrations (ac-database-changes), not for distributed consensus across nodes (ac-distributed-state-and-replication), not for queue and workflow delivery semantics (ac-durable-execution).

jiayaoqijia Updated 81 repo stars

File contents

jiayaoqijia/cryptoskill commit 0d54dbdf3b

Frequently asked questions

npx get-skill add jiayaoqijia/ac-transaction-isolation