Incorrect warning on Rule 4207: Consider resequencing conditional logic for better performance (4333861)

Incorrect warning on Rule 4207: Consider resequencing conditional logic for better performance

A simple IF statement gives 5 warnings on Rule 4207. How to avoid this warning without disabling this rule.
Example : IF NVL( p_object.objectkey.TYPE, 5 ) <> 5 THEN

WORKAROUND

None

STATUS

Issue fixed in version 12.10. The latest version of Toad for Oracle can be downloaded here

TOR-892

Former CR118435 we can fix the issue where it's appearing five times; however, we don't think there's a way to have it not identify the "is better written as" IF statement. This rule is primarily designed to catch situations where the conditional logic "could possibly benefit from resequencing" (from the code's documentation). It's not designed to recognize if the code entered is already written in the most optimized method. There are too many variables that could determine that outcome. So, we simply flag the logic statement as something for the user to look at and possibly revisit. Anyway we updated the code so that it will only report the violation once, rather than multiple times.