SQLE 1.2206.0-pre1 Release Notes and New Feature Overview
The preview release SQLE 1.2206.0-pre1 introduces TiDB audit plugin support, TiDB‑specific rules, enhanced SQL syntax checks, and recommendations on primary‑key usage, while providing full release details, documentation links, and references to prior versions for database administrators and developers.
SQL audit tool SQLE 1.2206.0-pre1 was released today as a preview version; it is intended for trial of new features and does not guarantee a smooth upgrade.
Project Introduction SQLE is an open‑source SQL audit platform for database users and administrators. It supports multiple audit scenarios, a standardized release workflow, native MySQL auditing, and can be extended to other database types. Resources are listed below:
Type
URL
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 Edition Demo
http://124.70.158.246:8888/ (admin / admin)
Enterprise Edition Demo
http://124.70.158.246:8889/ (admin / admin)
New Version Main Features
1. TiDB audit plugin support (Enterprise). The plugin incorporates most MySQL audit rules while removing TiDB‑incompatible scenarios, making SQLE fully compatible with TiDB.
2. TiDB‑specific audit rules (Enterprise), including:
GROUP BY must contain all non‑aggregated columns from SELECT (enforces MySQL ONLY_FULL_GROUP_BY).
GROUP_CONCAT() syntax must use ORDER BY.
LIMIT pagination queries must include ORDER BY.
Prohibits inserting explicit values into auto‑increment primary keys.
Recommends avoiding auto‑increment keys for high‑concurrency tables, suggesting BIGINT with AUTO_RANDOM instead.
Examples and rule screenshots are shown in the following images:
Full Release Information
Features
[#565] Support for TiDB database audit (Enterprise)
[#573] Add four TiDB‑specific rules (Enterprise)
Bug Fixes
[#563] Fixed crash when SQLE scanner parses MyBatis XML with empty otherwise tag
Previous versions (1.2205.0, 1.2204.0, 1.2203.0) are linked for reference, along with recommended reading on common SQL development rules, using SQLE for various databases, MySQL 8.0 compatibility testing, custom rule development, and development‑stage SQL auditing.
For more information and community discussion, join the official QQ group: 637150065 .
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
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.
