Database design principles for Oracle. Schema design, indexing strategy, query optimization.
Database design principles for Oracle banking systems. Learn to THINK, not copy SQL patterns.
Read ONLY files relevant to the request! Check the content map, find what you need.
| File | Description | When to Read |
|---|---|---|
schema-design.md | Normalization, PKs, relationships, Oracle types | Designing schema |
indexing.md | Oracle index types, composite indexes, partitioning | Performance tuning |
optimization.md | EXPLAIN PLAN, hints, N+1, query tuning | Query optimization |
| Need |
|---|
| Skill |
|---|
| DDL generation | @[skills/oracle-ddl-generation] |
| CRUD packages | @[skills/oracle-package-crud-generation] |
| Report packages | @[skills/oracle-package-report-generation] |
10-database-naming-convention)RECORD_STAT, AUTH_STAT, MAKER_ID, CHECKER_ID, etc.)Before designing schema:
10-database-naming-convention naming rules?12-logical-data-modeling-rule for data modeling standards?❌ Use ORM instead of PL/SQL packages
❌ Skip indexing on foreign keys
❌ Use SELECT * in production queries
❌ Store JSON when structured columns are better
❌ Ignore N+1 queries in application code
❌ Create tables without audit columns