What problem does it solve? Generated mariadb-binlog commands often contain subtle errors: treating commented pseudo-SQL as replayable statements, stripping the base64 BINLOG blob, using the removed --position flag, or replaying output back into a server without disabling binary logging. This Skill encodes the MariaDB-specific behaviors and traps so commands for reading, filtering, and replaying binary logs are correct. ## Core Features & Use Cases - Correct replay patterns: Pipe decoded output into the mariadb client (never execute via the tool itself), use --disable-log-bin when replaying onto the source server, and keep the default --base64-output=auto so output stays re-executable. - MariaDB-specific features: Covers ANNOTATE_ROWS_EVENT original-SQL comments (printed by default) and --flashback for generating reverse/undo SQL for DML, including its constraints (binlog_row_image=FULL, incompatible with --raw and -v/-vv). - Filtering guidance: Position, datetime, GTID, server-ID, and domain-ID filtering, plus the local-only and format-dependent behavior of --database and the -R requirement for remote reads. - Use Case: After an accidental table update, generate a flashback undo script with mariadb-binlog -d test -T mytable --start-datetime=... --flashback, review it, and apply it with the mariadb client. ## Quick Start Ask the AI to write a mariadb-binlog command that extracts events from a specific time window of a binary log file and safely replays them into the mariadb client.
