Rules tagged with: Hint
Optimizer Hint usages.
All 6 check SQL or PL/SQL code (G- codes). Browse the rules below for explanations, examples and recommended fixes.
All 6 Hint rules
-
G-9600 Never define more than one comment with hints.Critical Reliability
-
G-9601 Never use unknown hints.Critical Reliability
-
G-9602 Always use the alias name instead of the table name.Critical Reliability
-
G-9603 Never reference an unknown table/alias.Critical Reliability
-
G-9604 Never use an invalid stats method.Critical Reliability
-
G-9605 Never use an invalid stats keyword.Critical Reliability
6 total
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.