Audit rows without triggers using MariaDB system-versioned tables
MariaDB system-versioned tables keep automatic row history so you can query past states without writing audit triggers.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
MariaDB system-versioned tables keep automatic row history so you can query past states without writing audit triggers.
Want to see what a row looked like yesterday? MariaDB’s system‑versioned tables keep every change automatically. This post walks through how they work, a point‑in‑time query example, the unbounded‑history trade‑off, and how to prune history with partitions.
MariaDB's system-versioned tables automatically capture every UPDATE and DELETE, letting you query any row as it existed at a past timestamp — no audit triggers or soft-delete logic required.
MariaDB 10.3+ system-versioned tables preserve every row version automatically. Learn the WITH SYSTEM VERSIONING syntax, FOR SYSTEM_TIME queries, history partitioning, and storage pitfalls.