This tutorial explains how to operate MySQL from Python using three different techniques—plain procedural code, object‑oriented classes, and modular imports—while covering __name__ handling, command‑line arguments, transaction management, and practical banking transfer examples.
This article provides a comprehensive overview of SQLite, covering its file‑based embedded architecture, type affinity, core components, supported data types, essential API functions, transaction management, and techniques for storing and retrieving binary data in embedded applications.
This article explains RocketMQ's core features—including ordered and duplicate message handling, transaction messages, producer and consumer mechanisms, storage architecture, indexing, subscription models, and practical best‑practice recommendations—while providing code examples and design insights for building scalable, high‑throughput distributed messaging systems.
The article explains why a MySQL UPDATE statement took five seconds by examining binlog entries, distinguishing slow‑query scans from lock‑waits, and using a Bash script to identify long‑running transactions that reveal hidden lock contention.
This article explains how MySQL binlog timestamps are derived from the THD start_time, why all events in a transaction share the same timestamp, how exec_time is calculated, and demonstrates the effect of autocommit and manual commit on binlog timing through concrete examples and source code analysis.
This article explains MySQL InnoDB's locking mechanisms—including MVCC snapshot vs. current reads, two‑phase locking, isolation levels, lock types, GAP locks, and deadlock scenarios—by analyzing simple and complex SQL examples and showing how different index and isolation configurations affect lock acquisition.
This article dissects the InnoDB transaction structure defined in storage/innobase/include/trx0trx.h, detailing each of the 63 variables—including their types, purpose, and interaction with MySQL’s transaction coordinator—so readers can grasp how InnoDB ensures data consistency and manages transaction state.
This article explains why locks are needed in multi‑user environments, describes common conflict types such as lost updates and dirty reads, compares pessimistic and optimistic locking mechanisms, shows practical implementations with version numbers and SQL Server locks, and presents a classic financial‑system case study.
This article explains the four MySQL isolation levels, their effects such as dirty reads, non‑repeatable reads and phantom reads, shows how to view and change the isolation level, and reviews the ACID principles of atomicity, consistency, isolation, and durability.
The article explains how concurrent transactions can cause deadlocks when resources are locked, and introduces the Actor model—combining data, behavior, and message passing—to give data its own active logic, thereby naturally handling concurrency and avoiding such deadlocks.
Facing high maintenance costs, complex business demands, and costly Microsoft tech, a company migrated its five‑year‑old transaction platform to Java, employing phased refactoring, comparative testing, and traffic‑splitting to ensure correctness, minimal impact, and a smooth, zero‑downtime rollout with centralized configuration and logging.
This article explains the internal structures and roles of Oracle undo and redo logs in transaction processing, walks through practical experiments that dissect undo segment headers, undo blocks, undo chains, redo records, fast‑commit behavior, and the true nature of DELETE operations, and shows how these insights help diagnose ORA‑600 startup failures.
This article presents a comprehensive technical overview of TiDB, a NewSQL distributed database, covering its architecture, SQL layer, KV engine, distributed transaction mechanisms, code implementation in Go, open‑source practices, and future roadmap.
This article explores how to maintain data consistency across services by using local transactions, two‑phase commit distributed transactions, and reliable message‑queue patterns, illustrating each method with an Alipay‑to‑YuEBao transfer example and discussing their trade‑offs.
This article explains why ALTER TABLE statements can become blocked by MySQL’s metadata locking, describes the underlying mechanisms, outlines common scenarios that cause “Waiting for table metadata lock,” and offers practical steps to diagnose and avoid such lock contention.
