SQLE 1.2205.0 Release Notes: New Features, SQL Auditing Enhancements, and Full Release Information

SQL audit tool SQLE version 1.2205.0 has been released, offering new functionalities, workflow optimizations, and bug fixes.

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.

Resources

Type

Link

Repository

https://github.com/actiontech/sqle

Documentation

https://actiontech.github.io/sqle-docs-cn/

Release Info

https://github.com/actiontech/sqle/releases

Audit Plugin Docs

https://actiontech.github.io/sqle-docs-cn/3.modules/3.7_auditplugin/auditplugin_development.html

Online Demo

http://124.70.158.246:8888/ (admin/admin)

New Version Main Features

The release adds three new capabilities and refines the SQL audit work‑order process, reducing workflow bottlenecks and supporting more exception scenarios. Highlights include Oauth2 login integration, LDAPS support, and secure SQL query auditing.

1. Enable Audited SQL Queries When enabled, only SQL statements that pass the audit can be executed; queries with audit suggestions at the warn level or higher are blocked.

2. Semantic Rule Testing Example: configuring a rule to forbid SELECT statements demonstrates how the tool rejects non‑compliant queries.

3. Database‑State Rule Testing A dynamic rule can block large table scans by setting a maximum row‑scan threshold (e.g., 10,000 rows). Creating a test table without primary keys or indexes and inserting over 10,000 rows triggers the rule.

Full Release Notes

Features

[#470] Support Oauth2 login integration (Enterprise edition)

[#250] LDAPS (LDAP over SSL) support for user integration

[#509] Support SQL query auditing (Enterprise edition)

Optimizations

[#471] Simplified configuration of audit task timing

[#474] Improved audit level messages for MySQL syntax parsing failures

[#504] Clearer error messages for gh‑ost dry‑run failures

[#517] Work‑order detail page now shows data source and database info

[#545] Limited work‑order description length to 50 characters

Bug Fixes

[#499] Fixed issue where tables named with reserved keywords broke audit display

[#302] Fixed MyBatis XML parsing errors for certain formats

[#502] Resolved DDL audit errors introduced in v1.2205.0‑pre1

[#524] Fixed Oracle Top SQL retrieval failure after database selection

[#516] Resolved UI overflow when work‑order description is too long

[#557] Fixed truncation of long custom rule threshold descriptions

Previous versions and additional reading links are provided for reference.