Why is this an issue?
WHERE clause conditions that reinforce or contradict the definitions of their columns are useless; they are always either
unconditionally true or unconditionally false. For instance, there’s no point in including
AND column IS NOT NULL if the column is
defined as non-null.
This rule raises issues only when a Data Dictionary is provided during the analysis. See https://docs.sonarqube.org/latest/analysis/languages/plsql/
Noncompliant code example
CREATE TABLE product
name VARCHAR(6) NOT NULL,
SELECT name, price
WHERE name is not null -- Noncompliant; always true. This column is NOT NULL
AND mfg_name = 'Too long name' -- Noncompliant; always false. This column can contain only 6 characters