Static code analysis for plsql files

The result of the analysis shows directly in the editor as hints. The static code analysis can also be started as a separate job from the project node.

Performance

• SQL statements that contains PL/SQL calls

Security

• Dynamic statement must be approved
• General_SYS.Init_Method should never be used in plsql files

Installability

• Oracle Enterprise Edition feature

Maintainability

• Annotation requires correction.
• Annotation requires correction.
• END name is different from method name
• IFS naming standard should be followed
• Keyword should be avoided as a Name
• Method argument ${object name} is not used.
• Method has too many statements
• Method without implementation
• Method/View duplicated with same signature
• Name is the same as another object's name
• Private method access in a different package
• The name is longer than the allowed maximum of 30 characters.
• Unused ${rule name} ${object name}.

Functionality

• $NULL to be used with $SEARCH/$TEXTSEARCH
• Binary functions cause translation issues
• Comparing with NULL always returns false
• Comparing with NULL is always false
• Comparison with the same field
• Conditional Compilation statement $ELSE is missing.
• Conditional Compilation statements require correction.
• Deprecated annotation has no functionality.
• Duplicate message definition validation
• Exist method call without boolean argument
• Global constant declaration
• Global variable declaration
• IFS translation standards should be followed
• IFS translation standards should be followed
• Method overtakes should be avoided
• Missing annotation or wrong usage of annotation.
• Not allowed to prefix DB calls with IFSAPP
• Pragma Error number should be minus integer
• String literals with non-US-ASCII characters
• Transactional statement approval
• Use count(*) instead of count(1).
• Use TO_CHAR() function
• VARCHAR2 length should be integer value

This page is generated from IFS Developer Studio at 2021-08-13 08:40.