Rules for PL/SQL that need database properties

[omoreno (Oscar Moreno)]

Hello,
at the link: https://docs.sonarqube.org/latest/analysis/languages/plsql/ specifies that “Some rules raise issues only when a data dictionary is provided during analysis” and "To provide a data dictionary, you must define the following properties … "properties of the database.
How can I know what rules need those parameters and what rules do not? In some companies, knowledge of these parameters is sometimes restricted by security and it is not possible to know them. So, for this reason, I would like to know what rules will be operational without these properties.

Thank you so much.

[pynicolas (Pierre-Yves Nicolas)]

As of today, only a few rules use the data dictionary:

• Inserts should include values for non-null columns
• Individual “WHERE” clause conditions should not be unconditionally true or false
• Nullable subqueries should not be used in “NOT IN” conditions
• Strings should only be moved to variables or columns which are large enough to hold them

[omoreno (Oscar Moreno)]

Hi Pierre-Yves,
thanks you so much for the answer. It helps me a lot.

Have a great weekend.

Kind regards.