Skip to content

README.md

Latest commit

 

History

History
52 lines (35 loc) · 2.43 KB

README.md

File metadata and controls

52 lines (35 loc) · 2.43 KB

APEX Standards Tracker Project

How to Contribute

DM Hayden @haydenhhudson on Twitter.

Introduction

In this repo, I am recording methods and queries to track and enforce APEX standards (including in the supporting database objects).

The Application Standards Tracker

In this repo, I have included a modified copy of the Application Standards Tracker, an application that was formerly included in the APEX Sample App Gallery. I have modified the application to expand it's use to cover enforcing coding standards in the supporting database objects (tables, views, packages, etc).

Installation

Per the standard of the Insum Starter Template, the installation script is release/_release.sql.

To clear your space of possible conflicts, you can run the deinstall script.

I've recorded a short video to document the installation: How to Install the Application Standards Tracker.

Modifications to support DB object coding standards

  1. Test assertion queries are now required to be stored as views in the database, instead of as clobs in the eba_stds_standard_tests table. This is a personal preference but has many advantages:
    • the code can now be studied / referenced / corrected outside of the application (eg, merely accessing this repo in a browser allows you to study them)
    • asserting the format of the test assertion queries is simpler this way (eg, requiring field names and their order)
    • reduced risk of SQL injection / XSS attacks from evaluating query stored as a clob
  2. I added "Database Supporting Object" to the "TEST LINK TYPES" LOV.

How to use PLScope

PL/Scope creates the following database objects :

  • dba/all/user_identifiers (since 11.1)
  • dba/all/user_statements since 12.2 These tables get populated only with the PL/SQL that compiled in sessions which have the following setting:
ALTER SESSION SET PLSCOPE_SETTINGS = 'IDENTIFIERS:ALL';

In order to compensate for the absence of PL/SQL that may have been compiled in different sessions without this plscope_settings value, it may be necessary to run the following command:

begin
    dbms_utility.compile_schema(schema => user, compile_all => true);
end;

How to contribute

I am happy to add anyone who asks as a contributor to repo

fixed a bug

set session state protection to 'unrestricted' for both P19_VALIDATE and P20_VALIDATE