SQLE 1.2204.0 Release Notes – New Features, Improvements, and Bug Fixes

SQL audit tool SQLE version 1.2204.0 has been released, and this article provides a detailed interpretation of its release notes.

Project Introduction – SQLE is an open‑source SQL audit platform for database users and administrators, supporting multi‑scenario audits, standardized release processes, native MySQL auditing, and extensible database types. The project repository, documentation, release information, audit‑plugin development guide, and an online demo (admin/admin) are listed in a table.

New Version Main Features

1. SQL Deployment Workflow Optimization : The community edition now includes an approval stage, allowing project‑specific approval permissions.

2. gh‑ost Usage Optimization : A dry‑run operation is performed during the audit stage to reduce failure rates; successful dry‑run prompts the user that gh‑ost will be used for online DDL, while failures display detailed error information.

3. Real‑time Message Push for Audit Tasks : Audit results can be pushed via email (community edition) or webhook (enterprise edition), enabling immediate notification of audit reports, such as in slow‑log audit scenarios.

Complete Release Information

Features

[#441] gh‑ost usage optimization with dry‑run and audit suggestions.

[#442] Mybatis Scanner adds a CLI flag to skip unparsable SQL.

[#429] Audit task detail page now shows audit time, pass rate, and score.

[#453] Permission system enhancements: new work‑order approval permission, default workflow includes approval step, and granular audit‑task permissions.

[#448] Message push for audit results (email for community, webhook for enterprise).

[#463] Mybatis XML audit now supports iBatis XML files.

Improvements

[#469] Optimized layout of the "Applicable Databases" column in rule template UI.

Bug Fixes

[#425] Fixed errors caused by excessively long SQL text during audit.

[#443] Fixed MySQL charset/collation mismatch issue.

[#449] Resolved permission issue when viewing work orders across multiple data sources.

[#465] Fixed inaccurate results for the "Suggest optional fields over threshold as index" rule.

Previous versions (1.2203.0, 1.2202.0, 1.2201.0, etc.) are linked for reference, along with recommended reading on MySQL 8.0 compatibility, custom rule development, and SQLE usage in development stages.