Languages available for analysis include PL/SQL and T-SQL.
In our project, we have a number of scripts targeting MySQL 8.0. These have the extension .sql, so scans were (by default) attempting to parse as PL/SQL.
Unfortunately, I wasted a couple of hours trying to understand why code that looked valid and was working was causing parse errors during analysis.
It would be valuable if there were a sensor configured for MySQL syntax. For now, I’ve changed the PL/SQL settings to avoid attempting analysis on .sql files, and I have to rely on manual techniques to ensure quality.
NOTE: I understand that support for MySQL as the storage for SonarQube was dropped a couple of years ago. This request is about the language of the source code to be analyzed.