Repository navigation
v0.23.12
English
BinlogViz v0.23.12 Release Notes
Release date: 2026-10-03
Overview
v0.23.12 names transaction identity on the default text, Markdown, and HTML analyze reports. Each transaction lists server_id, thread_id, GTID, and xid or XA xid when the events have them. user@host appears only when the binlog stored an invoker. A field the events do not have stays absent: no 0, no empty string. JSON already had these fields. --sql-context full is unchanged. Workflow and trend behavior are unchanged.
New Features
- Transaction identity on text, Markdown, and HTML (#104): Default text, Markdown, and HTML analyze reports name, per transaction,
server_id,thread_id, GTID, andxidor XA xid when the events have them. The tokens areserver_id=,thread_id=,gtid=,xid=, andxa_xid=for whichever of those the transaction carries.user@host=appears only when the binlog stored an invoker. A missing field stays absent (no0, no empty string). The MySQL 8.0.46FLUSH TABLESfixture printsserver_id=1,thread_id=12, its GTID, andxid=16, and does not printuser@host.minimal.binlogprintsserver_id,thread_id, andxid, and does not printgtid=oruser@host. JSON already had these fields and still omits an empty one.--sql-context fullis unchanged.
Verification
BinlogQA dogfood on tip 72cd660 (#104): PASS on 2026-10-03.
Breaking Changes
None.
Compatibility
- Exit codes 0, 1, and 2 keep ADR-0001 meaning.
- JSON transaction identity is unchanged.
--sql-context fullis unchanged. - CLI flags, snapshots, workflows, artifact names, and supported platforms are otherwise unchanged from v0.23.11.
- Workflow and trend behavior are unchanged.
中文
BinlogViz v0.23.12 发布说明
发布日期:2026-10-03
概述
v0.23.12 在默认文本、Markdown 和 HTML 的 analyze 报告里按事务写出身份。事件里有的 server_id、thread_id、GTID,以及 xid 或 XA xid,会写出来。user@host 只在 binlog 存了调用方时出现。事件里没有的字段保持缺席:不写 0,也不写空字符串。JSON 本来就有这些字段。--sql-context full 不变。workflow 与 trend 行为不变。
新功能
- 文本、Markdown 和 HTML 写出事务身份(#104):默认文本、Markdown 和 HTML 的 analyze 报告按事务写出事件里有的
server_id、thread_id、GTID,以及xid或 XA xid。记号是事务实际带上的server_id=、thread_id=、gtid=、xid=和xa_xid=。user@host=只在 binlog 存了调用方时出现。缺的字段保持缺席(不写0,不写空字符串)。MySQL 8.0.46 的FLUSH TABLESfixture 会写出server_id=1、thread_id=12、它的 GTID 和xid=16,不写user@host。minimal.binlog写出server_id、thread_id和xid,不写gtid=或user@host。JSON 本来就有这些字段,空的仍然省略。--sql-context full不变。
验证
BinlogQA 在 tip 72cd660(#104)上的 dogfood:2026-10-03 PASS。
破坏性变更
无。
兼容性说明
- 退出码 0 / 1 / 2 仍按 ADR-0001。
- JSON 的事务身份不变。
--sql-context full不变。 - CLI 参数、快照、工作流、产物命名和支持平台除此之外与 v0.23.11 一致。
- workflow 与 trend 行为不变。