Rules tagged with: Function Usage
Usage of provided functions.
All 4 check SQL or PL/SQL code (G- codes). Browse the rules below for explanations, examples and recommended fixes.
All 4 Function Usage rules
-
G-9010 Always use a format model in string to date/time conversion functions.Blocker Security
-
G-9020 Try to use a format model and NLS_NUMERIC_CHARACTERS in string to number conversion functions.Critical Reliability
-
G-9030 Try to define a default value on conversion errors.Major Maintainability
-
G-9040 Try using FX in string to date/time conversion format model to avoid fuzzy conversion.Blocker Reliability
4 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.