Article directory
Why do you need a sql auditing platform?
During the collaborative development of a system, there are often changes to the data table, adding fields, modifying data, inserting data, and so on. These sqls are generally saved in a file separately and executed together when the system is upgraded. However, as the system grows larger and the number of developers increases, these SQLs are not always easy to save, or they are executed in a mess, which is very difficult to maintain.
The sql audit platform solves the above problems very well. This is an approval system, and the roles can be divided into developers, DBAs, and operation and maintenance personnel. The developer submits the sql that needs to be executed during the upgrade. These sql are reviewed by the DBA or the company's boss (must be reviewed, if there is an operation to delete the whole table, it will be a bad thing). After the review is passed, the operation and maintenance personnel click to execute.
Yearning - Automation, SQL Auditing
Yearning provides various functions such as query auditing, SQL auditing, SQL rollback, and custom workflow. The back-end is implemented in Go language, and the front-end uses the VUE framework. Has the following functions
- Automated SQL statement auditing, which can automatically detect and execute SQL
- A rollback statement is automatically generated after the DDL/DML statement is executed
- Audit/Query Audit function
- Support LDAP login/DingTalk and email message push
- Support for custom review workflows
- Support fine-grained permission assignment
Yearning is currently compatible with 99% of Mysql standard SQL syntax. However, due to the limitation of audit logic and other factors, it is not guaranteed to get correct feedback for some SQL statements. The known unsupported statement types are:
- Complex query statements (multiple tables, multiple functions, not required. Not all complex statements are not supported)
- Foreign key related statement
- Rollback of cross-repository DML statements is not supported
- Stored Procedure/Trigger
Functional interface
Note:
Yearning's official website is suitable for collaborative development by more people. It is used when sql is not easy to maintain. When there are two or three people, there is no need to superfluous.