Databases 6 min read

SQLE 2.2304.0-pre2 Release Notes – Project Overview, New Features, and Full Release Information

The article introduces the SQLE 2.2304.0-pre2 preview release, outlines the tool’s purpose for database users and administrators, details new enterprise‑level features such as affected‑row statistics and enhanced rule severity display, lists added MySQL audit rules, and provides complete release information and resource links.

Aikesheng Open Source Community
Aikesheng Open Source Community
Aikesheng Open Source Community
SQLE 2.2304.0-pre2 Release Notes – Project Overview, New Features, and Full Release Information

SQLE 2.2304.0-pre2 Release Notes

SQL audit tool SQLE 2.2304.0-pre2 is released as a preview version for trial use; smooth upgrade is not guaranteed.

1. SQLE Project Introduction

SQLE, an open‑source project from the Aikexing community, is a SQL audit tool for database users and administrators that supports multiple audit scenarios, 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 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://demo.sqle.actionsky.com (admin/admin)

Enterprise Edition Demo

http://demo.sqle.actionsky.com:8889 (admin/admin)

2. New Version Feature Highlights

1. SQL Analysis Adds Affected Row Count (Enterprise)

The platform now shows the actual affected row count in the SQL analysis panel, allowing users to evaluate execution performance; currently supported for MySQL, with Oracle, PostgreSQL, and SQL Server support planned.

2. Audit Results Emphasize Rule Severity and Count

Audit result columns now prioritize displaying the severity level and number of triggered rules, helping users quickly assess rule impact.

3. New Batch of MySQL Audit Rules

Check if LIMIT offset is excessively large.

Require WHERE clause for UPDATE/DELETE statements.

Prohibit overuse of bind variables.

Enforce join conditions.

Recommend COUNT(*) over COUNT(col).

Require NOT NULL constraint on indexed columns.

Avoid full index scans in execution plans.

Avoid index jump scans.

Warn when UPDATE/DELETE affect too many rows.

Prohibit sorting on long VARCHAR fields.

3. Complete Release Information

Added

[#1413] New SQL affected‑row hint (Enterprise).

[#1432] New batch of MySQL audit rules.

Features

[#1427] Audit results highlight rule severity and count.

[#1412] Various UI optimizations.

For previous versions and additional reading, see the linked articles and resources at the end of the document.

SQLMySQLdatabase auditingDatabase ToolsRelease NotesSQLE
Aikesheng Open Source Community
Written by

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.

0 followers
Reader feedback

How this landed with the community

login Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.