16
CREATE OR REPLACE PACKAGE valstd
IS
PROCEDURE progwith (str IN VARCHAR2);
PROCEDURE pw_rae;
END valstd;
/
You can now call valstd.pw_rae to show all the "programs with"
RAISE_APPLICATION_ERROR (as you can easily see from the valstd package body).
You can also call valstd.progwith to search for other strings. If, therefore, You've a
standard that developers should never hard-code -20,000 error numbers, issue this
command:
SQL> exec valstd.progwith ('-20')
and view what is likely to be a superset of all such instances.
Another kind of standard that might be set within an organization is that application
code should never reference a table or view directly but instead always go through
an encapsulation package ([SQL-01: Qualify PL/SQL variables with their scope names
when referenced inside SQL statements.]). Here is a query that identifies all program
units that violate this rule:
SELECT owner || '.' || name refs_table,
referenced_owner || '.' ||
referenced_name table_referenced
FROM all_dependencies
WHERE owner LIKE UPPER ('&1')
AND TYPE IN ('PACKAGE',
'PACKAGE BODY',
'PROCEDURE',
'FUNCTION')
AND referenced_type IN ('TABLE', 'VIEW')
ORDER BY owner,
name,
referenced_owner,
referenced_name;
Benefits
You don't have to rely solely on "manual" walkthroughs of code to validate
compliance with group standards.
Code analysis and code "mining" (extracting information from/about source code)
can be automated and tightly integrated into the development process.
Challenges
You need to design and build the analysis code and then integrate these checks into
your ongoing development effort.
Resources
剩余197页未读，继续阅读
