PostgreSQL
Language-specific information about the way that SonarQube Cloud supports the analysis of PostgreSQL.
Last updated
Was this helpful?
Language-specific information about the way that SonarQube Cloud supports the analysis of PostgreSQL.
To discover and update the SQL-specific properties used for PostgreSQL analysis, navigate in SonarQube Cloud to Your Project > Administration > General Settings > Languages > SQL. See Configuration overview for more information about setting properties.
With the default configuration, files with the .pgsql and .psql file extensions are analyzed as PostgreSQL, and files with the .sql file extension are analyzed as PL/SQL. The .sql file extension can be associated with only one SQL dialect. This behavior is defined in Your project > Administration > General Settings > Languages > SQL > File Suffixes. You can override these properties at the project level.
Adding the -- NOSONAR comment at the end of the line will suppress all issues on that line.
Rather than relying on this method, we suggest refining your analysis scope to avoid creating major gaps in your code review. Because the NOSONAR comment silences all current and future issues on a line without regard for their severity, it is an imprecise tool. Even if you only intend to hide a minor stylistic point, you could unintentionally obscure a serious security flaw.
The rules NoSonar allows tracking in-line suppression comments in T-SQL code.
Last updated
Was this helpful?
Was this helpful?