ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Databases & messaging · #mariadb
MariaDB 10.3+ system-versioned tables automatically preserve row history, replacing manual audit tables and triggers with a queryable temporal log.
MariaDB stores JSON as LONGTEXT, not a binary type. This guide compares plain text, the JSON alias with validation, and generated-column indexing to help you pick a storage strategy.
Enable MariaDB system-versioned tables to automatically track every row change, query historical states with FOR SYSTEM_TIME syntax, and manage retention to control storage growth.
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.
Configure MariaDB Galera Cluster for synchronous multi-master replication: minimal three-node config, certification-based conflict resolution, DDL handling, flow control tuning, and operational limits.
An architecture note on when MariaDB Galera is the right high-availability choice: minimal three-node design, trust boundaries, the status variables that matter, failure modes, and when to pick async replication.
Learn how to run ALTER TABLE operations that avoid full table locks in MariaDB 10.0+, verify low impact, and recover if the operation stalls.
Step-by-step guide to deploying a three-node MariaDB Galera Cluster with synchronous multi-master replication, covering installation, configuration, bootstrap, verification, and recovery procedures for high-availability workloads.
Step‑by‑step architecture note for enabling InnoDB data‑at‑rest encryption in MariaDB: requirements, minimal design using keyring_file, trust boundaries, operational checks, failure modes, and triggers for redesign.
json