Reference · built on requestConnectorDatabases & warehouses

MariaDB Server

Tables, binary log events, and GTID positions from MariaDB Server through MariaDB Connectors.

Request accessPricing ↗

About

MariaDB Server is the relational database maintained by MariaDB plc. Applications connect with MariaDB Connectors for C, C++, Java, Node.js, Python, ODBC, R2DBC, and .NET; Connector/C keeps the same API as the MySQL client library, so tooling written for MySQL generally works. The binary log records every change to the databases and drives replication; its default format is MIXED, which falls back to row events where a statement is not replication-safe. Global transaction IDs take the form domain_id-server_id-sequence_number and let a reader resume from an exact position.

An operator on Fibric reads your tables and the binary log, keeps its own GTID position, and proposes row changes for your approval with a receipt you can reverse.

This is a reference listing. It documents what Fibric would read from MariaDB Server and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Rows from tables the account can SELECT, with database names listed by SHOW DATABASES where that privilege is granted
  • Row binlog events from the binary log, read by an account holding REPLICATION SLAVE (REPLICATION REPLICA in 10.5 and later)
  • The current binary log position through SHOW BINLOG STATUS and SHOW BINARY LOGS, granted by BINLOG MONITOR
  • GTID positions from gtid_binlog_pos, gtid_current_pos, and gtid_slave_pos, per replication domain
  • Replica state through SHOW REPLICA STATUS and SHOW RELAYLOG EVENTS, granted by REPLICA MONITOR

Proposed actions

  • Target capability: propose an INSERT or UPDATE against a named table through a MariaDB Connector, run once after approval
  • Target capability: propose a Flashback of a table to an earlier binary log point, where binlog_format=ROW and binlog_row_image=FULL are set

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Keep a warehouse copy current

    Read row events from the binary log, apply them to the analytics store, and store the GTID position so a restart resumes without a full reload.

    With Data Freshness, Operations Analyst

  • Catch a runaway job before it fills the disk

    Track SHOW BINARY LOGS sizes and table row counts per cycle and flag a table whose write rate jumps outside its usual band.

    With Anomaly Notice, Storage Growth

  • Undo a bad bulk update

    When rows were overwritten by mistake, propose a Flashback to the binary log position before the statement, with the affected row count shown for approval.

    With Root Cause

Requirements

  • A MariaDB Server with the binary log enabled by the --log-bin option
  • binlog_format=ROW on the source, since the MIXED default logs many statements as SQL text rather than row images
  • An account with SELECT on the tables to read plus REPLICATION SLAVE and BINLOG MONITOR for binary log access
  • MariaDB 10.5 or later for the BINLOG MONITOR and REPLICA MONITOR privilege names; older servers use REPLICATION CLIENT
Authentication
A MariaDB account using one of the server's authentication plugins: mysql_native_password for MySQL-compatible clients, ed25519, PARSEC, unix_socket, PAM, or GSSAPI.

Limits

  • With the default MIXED format, statement-logged changes carry no row images; only events logged as rows yield before-and-after values
  • Flashback reverses DML only (INSERT, DELETE, UPDATE); DROP, TRUNCATE, and ALTER cannot be undone from the log today
  • Purged binary logs cannot be replayed; a GTID position older than the oldest retained log forces a fresh snapshot

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request MariaDB Server ↗

Questions and answers

Is MariaDB wire-compatible with MySQL clients?
MariaDB Connector/C has exactly the same API as the MySQL Connector/C for MySQL 5.5, and the mysql_native_password plugin exists for MySQL-compatible clients. MariaDB describes Connector/C as connecting applications to both MariaDB and MySQL databases.
What privileges does binary log reading need?
REPLICATION SLAVE, aliased REPLICATION REPLICA since MariaDB 10.5, to receive updates from the primary; BINLOG MONITOR for SHOW BINLOG STATUS and SHOW BINARY LOGS; and REPLICA MONITOR, added in 10.5.9, for SHOW REPLICA STATUS and SHOW RELAYLOG EVENTS.
How does a reader resume after a restart?
By GTID. Each transaction carries domain_id-server_id-sequence_number, and the server exposes gtid_binlog_pos for the last event group written. The connector records the last GTID it applied and asks for events after it, the same way CHANGE MASTER master_use_gtid works for a replica.
Ask about MariaDB Server

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with MariaDB Server through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy