SQLE 1.2201.0-pre1 Release Notes – New Features, Fixes, and Resources
The preview release SQLE 1.2201.0-pre1 introduces audit workflow enhancements, fixes LDAP and MySQL schema issues, provides updated documentation and repository links, and offers several related reading links for the open‑source SQL audit tool aimed at database users and administrators.
SQL audit tool SQLE version 1.2201.0-pre1 was released today as a preview version; it is intended for trial use only and does not guarantee a smooth upgrade.
SQLE is an open‑source tool for database users and administrators that supports multi‑scenario audits, a standardized release process, native MySQL auditing, and extensible support for other database types.
Key resources include the GitHub repository ( https://github.com/actiontech/sqle ), documentation site ( https://actiontech.github.io/sqle-docs-cn/ ), release information page, and the audit‑plugin development guide.
Update List – Features : The audit workflow has been optimized so that only SQL statements that pass the audit can be submitted as tickets; this behavior is configurable and, by default, error‑level audit prompts block ticket submission.
Fixes : • Fixed an issue where LDAP users with non‑standard platform formats could not be edited via the UI. • Resolved a MySQL audit failure for schemas containing hyphens (e.g., "test-db").
Recommended reading links provide additional context on previous releases and new capabilities, such as SQLE 1.2112.0-pre1, timed releases, index optimization, and earlier version announcements.
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.
