Rule tags
Every dbLinter rule carries one or more tags that name its topic. The 229 rules use 28 tags, from broad themes such as Stored Object, Control and Performance to narrow ones such as Hint or Dynamic SQL. 11 of the tags are specific to Oracle APEX: they name the APEX component type a rule inspects, for example APEX_APPLICATION_PAGES.
Use a tag when you know the subject but not the rule code. The most common tags are Stored Object (34), Control (26), Performance (24), Variable (22) and SQL (21). To browse by impact instead of topic, see the severity levels or the quality areas.
All 28 tags
Stored Object
34 rules. Stored objects (packages, types, functions, procedures and triggers).
Control
26 rules. Control structures: cursors, conditionals and flow control.
Performance
24 rules. Efficient use of resources.
Variable
22 rules. Variables and data types.
SQL
21 rules. Integration of SQL (DQL, DML and TCL) in stored objects.
Naming SQL
19 rules. Naming conventions for SQL objects and identifiers.
Naming PL/SQL
16 rules. Naming conventions for PL/SQL identifiers.
General
13 rules. General topics.
Pattern
11 rules. Common programming patterns.
Exception
8 rules. Exception handling.
Modeling
8 rules. Database modeling and design.
APEX_APPLICATION_PAGE_REGIONS
7 rules. Component type APEX_APPLICATION_PAGE_REGIONS in UC APEX Project Eye.
APEX_APPLICATION_PAGES
7 rules. Component type APEX_APPLICATION_PAGES in UC APEX Project Eye.
APEX_APPLICATION_PAGE_ITEMS
6 rules. Component type APEX_APPLICATION_PAGE_ITEMS in UC APEX Project Eye.
Hint
6 rules. Optimizer Hint usages.
APEX_APPL_PAGE_IG_COLUMNS
5 rules. Component type APEX_APPL_PAGE_IG_COLUMNS in UC APEX Project Eye.
APEX_APPLICATIONS
5 rules. Component type APEX_APPLICATIONS in UC APEX Project Eye.
Observability
5 rules. Logging, tracing, debugging and monitoring.
PinkDB
5 rules. The Pink Database paradigm (PinkDB) is an application architecture for database-centric applications.
DD Query
4 rules. For optimum results, the check requires access to the data dictionary. Therefore, a read-only connection must be configured.
Function Usage
4 rules. Usage of provided functions.
APEX_APPLICATION_PAGE_BUTTONS
3 rules. Component type APEX_APPLICATION_PAGE_BUTTONS in UC APEX Project Eye.
Dynamic SQL
3 rules. Dynamic SQL.
Naming APEX
3 rules. Naming conventions for APEX identifiers.
APEX_APPLICATION_ITEMS
1 rule. Component type APEX_APPLICATION_ITEMS in UC APEX Project Eye.
APEX_APPLICATION_LISTS
1 rule. Component type APEX_APPLICATION_LISTS in UC APEX Project Eye.
APEX_APPLICATION_PAGE_BRANCHES
1 rule. Component type APEX_APPLICATION_PAGE_BRANCHES in UC APEX Project Eye.
APEX_APPLICATION_PAGE_VAL
1 rule. Component type APEX_APPLICATION_PAGE_VAL in UC APEX Project Eye.
Related rule collections
- Trivadis PL/SQL & SQL guideline rules - Rules that implement the Trivadis coding guidelines.
- OWASP-related security rules - Rules that name an OWASP Top 10 risk category.
- Oracle APEX rules - Checks for APEX applications, pages, items and regions.
- PostgreSQL rules - Rules that also apply to PostgreSQL and PL/pgSQL.
- Security rules - All rules in the Security quality area.
- Reliability rules - Rules that prevent bugs and failures at run time.
- Maintainability rules - Rules for code that is easy to read and change.
- Rule profiles - Essential to Extreme: which rules are checked.
- All rules - Search and filter the complete rule set.