Rules tagged with: Modeling
Database modeling and design.
All 8 check SQL or PL/SQL code (G- codes). Browse the rules below for explanations, examples and recommended fixes.
All 8 Modeling rules
-
G-1210 Never create a table without a primary key.Blocker Reliability
-
G-1220 Avoid composite primary keys.Major Maintainability
-
G-1230 Avoid tables without relationships.Major Maintainability
-
G-1240 Try to index foreign key columns.Major Reliability
-
G-1250 Try to define a business key for each table.Major Reliability
-
G-1260 Try to define a comment for each table.Info Maintainability
-
G-1270 Try to define a comment for each column.Info Maintainability
-
G-1280 Try to use domains instead of raw datatypes for table columns.Minor Maintainability
8 total
Related tags
Tags that appear on the same rules as Modeling:
- Performance (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.