Introducing SQLE: An Open‑Source SQL Quality Control Platform with Java Application Auditing
The article presents SQLE, an open‑source SQL quality‑control tool that supports end‑to‑end development, testing, and deployment, highlights new features in version 1.2202.0—including user‑group permissions, MySQL rules, and Java application auditing—and demonstrates a step‑by‑step integration workflow with code examples and screenshots.
1. SQLE Overview
SQLE is an open‑source project initiated by the ActionTech community that provides a complete workflow for SQL development, testing, and release, with fine‑grained resource and permission management, aiming to deliver a secure, reliable, and easily maintainable SQL quality‑control solution.
In the February 1.2202.0 release the following enhancements were added:
Redesigned user system with new user groups and operation permissions.
Scoring function for work‑order audit results.
Audit tasks supporting MySQL schema, Oracle TopSQL, and SQL capture/audit for Java applications.
Db2 audit plugin for reviewing and releasing Db2 work‑orders.
37 new MySQL audit rules, such as detecting redundant indexes in DDL.
Various usability improvements and bug fixes.
More details are available at the release page: GitHub Release v1.2202.0 .
2. Java Application Auditing
(Enterprise edition feature)
Starting with version 1.2202.0, SQLE supports SQL auditing for Java applications, allowing zero‑cost integration without modifying the application code.
Key features of SQLE’s Java auditing:
Non‑intrusive integration via environment variables, enabling SQLE to attach to a Java process without code changes.
Automatic SQL collection and statistics; users can view classification and metrics of application SQL in the SQLE statement pool.
Manual or automatic audit of SQL, providing reports that indicate compliance with predefined audit rules for developers and DBAs.
3. Demonstration Steps
Prepare the environment, the target Java application (e.g., SurveyKing ), and the associated database as a data source.
Create a Java application audit task in SQLE.
Start the application with SQLE collection enabled, for example:
SQLE_COLLECT_ENABLE=true
SQLE_HOST=XX.XX.XX.XX:10000 \
SQLE_TASK_NAME=surveryking_test \
SQLE_TASK_TOKEN=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJhcG4iOiJqd19hcHAiLCJleHAiOjE2NzcyMjYxNzcsIm5hbWUiOiJhZG1pbiJ9.3d0pA1hiVnFEWJokSFBwCT8d1pKOYV6SViENj4GFqgI \
java -jar surveyking-v0.3.0-beta.4.jar \
--server.port=1991 \
--spring.datasource.url=jdbc:mysql://XX.XX.XX.XX:3306/surveyking \
--spring.datasource.username=root \
--spring.datasource.password=xxxxxx \
& >> /opt/surveyking/std.logOpen the SQLE audit task detail page to view the SQL statements executed by the application.
Inspect the audit report to verify whether the SQL complies with the configured audit rules.
Create a user in the Java application; the corresponding INSERT statement will appear in the SQLE statement pool.
Use the statement‑pool page to quickly see classification and statistics of all executed SQL.
The demonstration shows that Java applications can be integrated with SQLE at zero cost, giving developers and DBAs full visibility of SQL audit results, execution status, and statistical information throughout the development‑to‑production lifecycle.
4. Further Resources
For more information about SQLE, visit:
Repository: https://github.com/actiontech/sqle
Documentation: https://actiontech.github.io/sqle-docs-cn/
Release information: https://github.com/actiontech/sqle/releases
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.