SQLE 2.2306.0-pre2 Release Notes: New Features, Enhancements, and Bug Fixes
The SQLE 2.2306.0-pre2 release introduces three new MySQL audit rules, configurable operation‑record expiration, expanded DB2 rule support, numerous optimizations and bug fixes, and provides download links, documentation, and demo environments for both community and enterprise editions.
SQL audit tool SQLE 2.2306.0-pre2 was released today; this article provides a detailed interpretation of the release notes.
Project Introduction – SQLE, an open‑source project from the Aikexing community, is a SQL audit tool for database users and administrators. It supports multiple audit scenarios, a standardized release workflow, native MySQL auditing, and extensible database types, currently offering more than 700 rule definitions.
Resources
Type
Address
Repository
https://github.com/actiontech/sqle
Documentation
https://actiontech.github.io/sqle-docs-cn/
Release Information
https://github.com/actiontech/sqle/releases
Audit Plugin Development Docs
https://actiontech.github.io/sqle-docs-cn/3.modules/3.7_auditplugin/auditplugin_development.html
Community Demo
http://demo.sqle.actionsky.com
Admin: admin Password: admin
Enterprise Demo
http://demo.sqle.actionsky.com:8889
User: admin Password: admin
New Features – Community Edition
Added three MySQL audit rules: (1) only one auto‑increment column per table; (2) discourage multiple joins on the same table; (3) require at least one index to have a NOT NULL constraint.
New Features – Enterprise Edition
Support for custom operation‑record expiration time (default 90 days, configurable to 30 days).
Steps to change expiration time:
Platform admin opens system settings → global configuration; default expiration is 2160 hours (90 days).
Modify the value to 720 hours (30 days) (see screenshot below).
Submit to save; records older than 30 days will be reclaimed.
Additional DB2 Support
The release adds comprehensive DB2 rule support, covering DDL, DML, DQL, usage recommendations, naming conventions, and index standards.
Full Release Information – Community Edition
New Features : Added three MySQL audit rules (see above).
Optimizations : Improved toggle interaction in system settings.
Bug Fixes : Fixed panic issue for rule “subquery does not support LIMIT”, corrected ineffective “too many columns” rule, resolved duplicate installation DingTalk notification problem.
Full Release Information – Enterprise Edition
New Features : Configurable operation‑record expiration; added 25 DB2 audit rules.
Bug Fixes : Fixed OceanBase for MySQL TopSQL empty‑value error; fixed incomplete parsing of MySQL slow‑log audit when SQL contains line breaks.
Previous versions are linked for reference, and several recommended articles are provided for deeper understanding of SQLE and SQL development rules.
For more information and community discussion, join the official QQ group: 637150065 .
Aikesheng Open Source Community
The Aikesheng Open Source Community provides stable, enterprise‑grade MySQL open‑source tools and services, releases a premium open‑source component each year (1024), and continuously operates and maintains them.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.