, , , ,

With MySQL now capable of features such as stored procedures and functions the need for tooling to support SQL code quality is greater than ever. A number of tools provide editors with syntax support and all the fancy features you’d expect from a modern IDE (see Toad as a leading product).

However the means to assess the quality of the procedures or scripts written for MySQL or the divergence from ISO standards doesn’t exist, although plenty of options exist for T-SQL (MS SQL Server), PL/SQL (Oracle) and even some tooling for DB2 and Informix.

The value of the static analysis tool means you can implement quality measures, controls and reporting through Continuous Integration tooling such as Jenkins, Sonar etc. All of which is a little ironic when you consider a lot of energy in CI (and Continuous Delivery appears to come from the open source community) which usually supports MySQL as one of the 1st options for databases.

Does this mean there is a gap in the market? Such capabilities dont seem to be in the MySQL WorkBench roadmap. Would love to know what people think?

Of course if you can support MySQL, then the offshoots such as MariaDB wouldn’t be too difficult.