
Relational Database Mini Project
Designed a normalized relational schema and wrote SQL queries using JOIN, GROUP BY, and aggregation; improved query efficiency through structured data modeling.
- Role ·
- Solo
The problem
Needed hands-on practice designing a schema that holds up under real query patterns — joins, aggregation, grouping — rather than just learning SQL syntax in isolation.
The approach
Designed a normalized (3NF) relational schema across users, orders, order_items, products, and payments, then wrote and refined SQL queries exercising JOIN, GROUP BY, and aggregation semantics against it.
Stack & why
- MySQL — widely-used relational engine, good fit for practicing standard SQL without vendor-specific syntax detours
Metrics
- 5-table 3NF schema (users, orders, order_items, products, payments)
- Query set exercising JOIN, GROUP BY, and aggregation
Architecture
A normalized schema (users, orders, order_items, products, payments) with clear foreign keys, plus a query set demonstrating JOIN, GROUP BY, and aggregation semantics.
Results
A working relational schema and query set, with structured data modeling that measurably simplified query logic (see the normalization journal post for the specific before/after).
What I learned
Schema design decisions are the difference between a query that reads cleanly and one that fights you — most SQL pain is a modeling problem wearing a syntax costume.
