Rules tagged with: Stored Object
Stored objects (packages, types, functions, procedures and triggers).
All 34 check SQL or PL/SQL code (G- codes). Browse the rules below for explanations, examples and recommended fixes.
Most severe Stored Object rules
- G-1310 Never keep database objects in an invalid state. Blocker
- G-7330 Always assign values to OUT parameters. Blocker
- G-7450 Never return a NULL value from a BOOLEAN function. Blocker
- G-7510 Always prefix Oracle supplied packages with owner schema name. Blocker
- G-7515 Always prefix Oracle supplied object types with owner schema name. Blocker
- G-7720 Never use multiple UPDATE OF in trigger event clause. Blocker
All 34 Stored Object rules
-
G-1310 Never keep database objects in an invalid state.Blocker Reliability
-
G-7110 Try to use named notation when calling program units.Major Maintainability
-
G-7120 Always add the name of the program unit to its end keyword.Minor Maintainability
-
G-7125 Always use CREATE OR REPLACE instead of CREATE alone.Major Maintainability
-
G-7127 Always use the FORCE option when creating views.Major Maintainability
-
G-7130 Always use parameters or pull in definitions rather than referencing external variables in a local program unit.Major Reliability
-
G-7140 Always ensure that locally defined procedures or functions are referenced.Major Maintainability
-
G-7150 Try to remove unused parameters.Major Maintainability
-
G-7160 Always explicitly state parameter mode.Major Reliability
-
G-7170 Avoid using an IN OUT parameter as IN or OUT only.Major Reliability
-
G-7180 Try to keep the complexity of functions, procedures and triggers simple.Critical Maintainability
-
G-7210 Try to keep your packages small. Include only few procedures and functions that are used in the same context.Minor Reliability
-
G-7220 Always use forward declaration for private functions and procedures.Minor Maintainability
-
G-7230 Avoid declaring global variables public.Major Reliability
-
G-7250 Never use RETURN in package initialization block.Major Reliability
-
G-7310 Avoid standalone procedures – put your procedures in packages.Minor Maintainability
-
G-7320 Avoid using RETURN statements in a PROCEDURE.Major Maintainability
-
G-7330 Always assign values to OUT parameters.Blocker Maintainability
-
G-7410 Avoid standalone functions – put your functions in packages.Minor Maintainability
-
G-7420 Always make the RETURN statement the last statement of your function.Major Maintainability
-
G-7430 Try to use no more than one RETURN statement within a function.Major Maintainability
-
G-7440 Never use OUT parameters to return values from a function.Major Maintainability
-
G-7450 Never return a NULL value from a BOOLEAN function.Blocker Maintainability
-
G-7460 Try to define your packaged/standalone function deterministic if appropriate.Major Reliability
-
G-7510 Always prefix Oracle supplied packages with owner schema name.Blocker Security
-
G-7515 Always prefix Oracle supplied object types with owner schema name.Blocker Security
-
G-7520 Avoid using deprecated units in your own code.Major Maintainability
-
G-7710 Avoid cascading triggers.Major Maintainability
-
G-7720 Never use multiple UPDATE OF in trigger event clause.Blocker Maintainability
-
G-7730 Avoid multiple DML events per trigger.Minor Reliability
-
G-7740 Never handle multiple DML events per trigger if primary key is assigned in trigger.Critical Reliability
-
G-7810 Never use SQL inside PL/SQL to read sequence numbers (or SYSDATE).Critical Reliability
-
G-7910 Never use DML within a SQL macro.Blocker Reliability
-
G-9501 Never use parameter in string expression of dynamic SQL. Use asserted local variable instead.Blocker Security
34 total
Related tags
Tags that appear on the same rules as Stored Object:
- Performance (8 shared)
- DD Query (2 shared)
- Dynamic SQL (1 shared)
More ways to browse rules
- 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.
- Rules by quality area - Security, reliability and maintainability.
- Rules by severity - From Blocker to Info.
- Rule profiles - Essential to Extreme: which rules are checked.
- All rules - Search and filter the complete rule set.