Page tree

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

On this page:

Target audience:

CAST AI Administrator

Summary: this page lists:

  • Impacts of changes made to CAST AIP 8.3.16 on Quality Model results post upgrade
  • Other impacts of changes made in CAST AIP 8.3.16

All changes in results related to extensions are now listed in the extension documentation and will not appear in this page.

Impacts of changes made in CAST AIP 8.3.16 on Quality Model results post upgrade

SAP / ABAP

SAP-172 - "CX_ROOT" should not be used in TRY .. CATCH.. ENDTRY block (8412)

The parent technical criterion for this rule was incorrectly set to "61020: Programming Practices - Modularity and OO Encapsulation Conformity", but it has been changed to "61014: Programming Practices - Error and Exception Handling". Therefore, after an upgrade to CAST AIP 8.3.16 and the generation of a post-upgrade consistency snapshot on unchanged source code, results may change. Grades for the new and previous parent technical criteria and Health Factors will change.

AIPCORE-961 - Avoid using AT Events in combination of LOOP AT .... WHERE constructs (7536)

The rule Avoid using AT Events in combination of LOOP AT .... WHERE constructs (7536) has been found to not function correctly in previous releases of CAST AIP. This bug has now been fixed, therefore, after an upgrade to CAST AIP 8.3.16 and the generation of a post-upgrade consistency snapshot on unchanged source code, results may change. You may have violations for this rule where previously there were none.

AIPCORE-279 and SAP-179 - multiple changes

Disabled rules

The following rules have been disabled in CAST AIP 8.3.16, therefore after upgrade to this release and the generation of a post upgrade consistency snapshot on unchanged source code, results may differ:

  •   Avoid using literals in assignments (hardcoded values) - 7522
  •   Avoid "SELECT *" queries (7344)

Source code bookmarks implemented

Bookmarks indicating the position of violations in the source code have been implemented for the following rules:

  • Avoid Artifacts with High Depth of Nested Subqueries (7130)
  • Avoid using BREAK or BREAK-POINT statement (7524)
  • Never use the ON CHANGE OF statement (7528)
  • Avoid "SELECT *" or "SELECT SINGLE *" queries (7530)
  • Avoid nested SELECT ... ENDSELECT statements (7532)
  • Avoid using AT events in combination of LOOP AT .... WHERE constructs (7536)
  • Avoid using SELECT ... INTO CORRESPONDING FIELDS OF (7538)
  • Avoid using SELECT ... ENDSELECT statement (7544)
  • Avoid using "ORDER BY" in SELECTS (7592)
  • Avoid using "SELECT DISTINCT", use DELETE-ADJACENT (7594)
  • Avoid using SELECT ... ENDSELECT statement on XXL tables (7666) 
  • Avoid using EXIT statement in Include (7672)
  • Avoid empty catch blocks (7788)
  • Avoid Artifacts with Group By (7806)
  • Avoid Artifacts with SQL statement including subqueries (7808)
  • Avoid Artifacts with a Complex SELECT Clause (7810)
  • Never use SQL queries with a cartesian product (7820)
  • Avoid Artifacts with queries on more than 4 Tables (7822)
  • Avoid using Native SQL (7882)
  • Avoid SQL queries that no index can support (7902)

Other impacts of changes made in CAST AIP 8.3.16

Oracle PL/SQL (embedded analyzer)

A change has been made to the way in which the analyzer handles the XMLROOT syntax (use of an "identifier" instead of "VERSION"). As a result of this change, after an upgrade to CAST AIP ≥ 8.3.16 and the generation of a post upgrade consistency snapshot on unchanged source code, you should expect many Oracle PL/SQL objects to be marked as modified.

  • No labels